What do you think about this Primary Key situation

Das Goravani das at Goravani.com
Tue May 5 13:37:04 EDT 2020


It is quite odd but here’s what’s happening:

I have an ex RSN field that is now in my SQL world as itself.. and in those RSN fields are the RSN values that were from Omnis.. so the records that were saved in Omnis and imported into my SQL database have a value in that field already.  Those inserted while the data was in SQL have a zero. 

I added rowid as a column in my schema and did a select with that schema.

The rowid column in the resultant table shows the Omnis value.. not the rowid

I assume this is because as it is said “A primary key becomes an alias of the rowid”

But it’s doing the opposite it is doing rowid as an alias for RSN field

Because it shows rsn as the label, and gives the value in the rsn field

It doesn’t show the label as rowid, it shows it as whatever the rsn primary key is named

And gives the value that is stored from Omnis in that field (column)

So I can’t get AT the rowid at all.. I can’t get it to load in a list because this rsn primary key alias takes over

How can I see the rowid if this thing keeps getting in the way

Do I have to remake my database tables with NO primary keys so that rowid will work?

I just want to pack rsn with rowid so that I have one unique field

I wonder if all the values in rsn were set to zero if rowid would finally show up but I doubt it

The records with zeroes in the rsn field had zeros in the results list when I fetched 


More information about the omnisdev-en mailing list