Re: rowid

Ed Schaefer wrote: > > Hi fellow Informix'ers: > > With the advent of 7.x online, Informix recommends not using rowid > since tables maybe fragments across dbspaces. Okay, I see no reason to > re-write a ton of 4GL code because of this if you're not planning on > fragmenting tables. Ed, 'INIT WITH ROWIDS' when altering a fragment on a table will create the rowid's for you. Thus, there is no need to rewrite your code. > > I've also heard a rumor that with 7.x, rowid is slower than using a key > into a table for select, insert, update, and delete purposes. Does > anyone have an opinion on that. > > Thanks! > > ed > schaefer Ed, I tend to disagree with this. Since, when a table gets fragmented it automatically gets its indexes fragmented as well. However, one could fragment a table and put the indexes in one db space. Thus, not fragmenting the index. This will also give better performance when large sequential scans take places. -- Jorge Torralba Intel Information Technology HF2-71 (503)696-4587 5200 NE Elum Yung Parkway Hillsboro, Or 97124 ===================================================== Any views or opinions expressed by me do not reflect those of Intel Corp.