Question Find by rowid without table

[ChrisJRutter]

If I have a rowid but don't know the table it relates to, is there any way to locate the record and then identify the table?

Other than doing this:
def var bh as handle.
def var fnd as logi.
def var rwid as rowid.

rwid = <a valid rowid>.

for each _file no-lock where not _hidden:

create buffer bh for table _file._file-name.
fnd = bh:FIND-BY-ROWID(rwid),NO-LOCK).
if fnd then
do:
message 'found' string(rwid) 'in table' _file._file-name.
leave.
end.
end.

 

[oli]

Forget it.

Throughout the ages, the uniqueness of a ROWID has changed.
Before v9, it was unique inside a database;
Since v9 is was unique inside a storage area;
A little bit later, it was unique inside a table;
Finally, "in OpenEdge 11, rowid's will not be unique per table either, if the database is multi-tenant" (Gus Bjorklund - http://communities.progress.com/pcom/message/138000#138000)

 

[TomBascom]

Horizontal partitioning will introduce yet another reason for it to be non-unique.

 

[Rob Fitzpatrick]

If I have a rowid but don't know the table it relates to, is there any way to locate the record and then identify the table?

Other than doing this:
def var bh as handle.
def var fnd as logi.
def var rwid as rowid.

rwid = <a valid rowid>.

for each _file no-lock where not _hidden:

create buffer bh for table _file._file-name.
fnd = bh:FIND-BY-ROWID(rwid),NO-LOCK).
if fnd then
do:
message 'found' string(rwid) 'in table' _file._file-name.
leave.
end.
end.

I don't understand how you end up with a rowid without knowing where it came from. Why are you storing it in a variable if you don't know which table it is in?

Also, your logic assumes that the first matching rowid is the "right" one. There is no reason for that to be necessarily true.

 

[TomBascom]

Error messages in log files is the main source for such things in my lfe...