Re: Informix vs Sybase(Urgent)

Yes, Informix does support limiting the number of rows fetched by a query. It's called C-ISAM, and my employer bought this product for this specific reason, and we used it quite successfully. Now, let's talk about Sybase and row-level locking! (oh but that's another matter....I guess Informix wins again!) peterwiley@hotmail.com wrote: > In article <Hxb8VvAY3MW1Ew$1@smooth1.demon.co.uk>, > David Williams <djw@smooth1.demon.co.uk> wrote: > > > > In article <3557F550.CB526222@agd.nsw.gov.au>, Anthony Mandic > > <no_sp.am@agd.nsw.gov.au> writes > > >Frank Chao wrote: > > [snip] > > > >> 3. Informix doesn't support any mechanism for limiting the number of > > >> rows > > >> fetched by a query (Sybase does this using the "set rowcount" feature). > > >> This > > >> is somewhat alarming since some queries could potentially select the > > >> entire > > >> database. There isn't a very good workaround for this problem, that I'm > > >> aware of. > > > > > True, Informix always gives you all the rows you ask for. > > While I haven't tried it, I reckon a SP using RESUME and a rowcounter to exit > the loop would work quite well in restricting the number of rows returned. You > could even pass in the max number of rows you wanted as one of the SPL input > parameters. > > Sounds to me like they don't know Informix very well. I'd question why you'd > *want* to use a BINARY datatype as a key, too. > > Peter Wiley > Currently hacking Oracle 7.3 on NT > > -----== Posted via Deja News, The Leader in Internet Discussion ==----- > http://www.dejanews.com/ Now offering spam-free web-based newsreading