Re: specifying number of rows to fetch
Re: specifying number of rows to fetch
- Subject: Re: specifying number of rows to fetch
- From: Georg Tuparev <email@hidden>
- Date: Sat, 3 Jul 2004 13:58:36 +0200
Better later then never...
This is somehow DB issue. Most databases support both the LIMIT and TOP
SELECT "options". In FrontBase (our all time preferred choice) we get
very good results using:
SELECT TOP(<skip value>, <count value>) ...
or just
SELECT TOP <count value> ...
have fun
gt
On Jun 29, 2004, at 12:57 AM, John Gilmore-Baldwin wrote:
I'm not sure there's a reliable way to do what you want without
resorting to database specific syntax and doing a raw row fetch with
custom sql.
There's also a question about accuracy. If you fetch rows 1-100, and
while you're looking at them "row" 50 is deleted, then you fetch rows
101-200, will a row get skipped? The answer to this question could
depend on your sort key, and whether it's unique. Similar issue for
inserts while looking at the data fetching the same row twice.
I'd suggest you consider limiting the result set to a certain number
of rows, and letting the users narrow their search if they get more
results (if this is feasible for you application).
John Gilmore-Baldwin
On Jun 28, 2004, at 4:55 AM, Goh Keng Boon wrote:
Actually i would like to fetch only 100 records into memory every
time, not so much on the ordering.
KB
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
Georg Tuparev
Tuparev Technologies
Klipper 13
1186 VR Amstelveen
The Netherlands
Mobile: +31-6-55798196
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.