Re: rowid no longer unique?

A simple upgrade with a DBA like me creating tables that are Fraggmented will break your code! So the best advice STOP USING ROWID in APPLICATION CODING!!! I just had to say this!!!! ------------------------------------------------------------------------- Cheryl Kendricks Internet:cherylk@prod1.jcdc.doleta.gov OR cherylk@gwysmtp.jcdc.doleta.gov DTSI, Inc. Voice: 1-800-598-5008 Fax: 512-393-7296 Database Administrator - DOL Job Corps San Marcos, Texas ------------------------------------------------------------------------ On Mon, 3 Jun 1996, Jonathan Leffler wrote: } It is not quite so simple as ROWID is no longer unique. } ....... } non-negligible overhead if the table is big enough to need fragmenting). } } So, you should avoid using ROWID in your code because it won't work for } every table in OnLine 7.x and above. } } Note that SE is not affected, and neither are non-fragmented tables, so you } have to go out of your way to break your code by making fragmented tables. } A simple upgrade from, say, 5.0x OnLine will not break your programs. } } Yours, } Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> } } >From: RonCichoski@msn.com (Ron ) } >Date: 31 May 96 21:44:23 -0700 } >X-Informix-List-Id: <news.24511> } > } >I think I remember seeing something in this bb about rowid no longer being } >necessarily unique within a table for v7. Is this true? More than once, } >while coding with ESQL, I coded a singleton select that I knew would return } >more than one row so I just added a where clause to avoid opening a cursor: } > } > select col from tab where rowid = } > (select max(rowid) from tab where key = "somevalue") } > } >Some purists might say that the model is not properly constructed if I have } >to do this but sometimes when you are dealing in the real world, well.... } > } >So, is it true? Thanks in advance. } > } >Ron Cichoski } >rcichoski@adventcon.com }