Re: SQL and retrieving the next xx rows

Yes, the problem I seem to be having is a UNION ALL. I added a FETCH FIRST
clause and I'm still getting all bazillion records into the result set.

I want to tell it "after 100 rows, just stop looking". But I suppose it's
not that easy using a union.

Here's my SQL now:

<!--SELECT CVINST, CVSFX, CVSRNM, CVGVNM, CVOTHN, CVDATE, CVINTP, CVSTAT,
CVBOOK, CVPAGE, 'con', RRN(RMSCONPF)FROM RMSCONPF WHERE CVINST >= 50000
UNION ALL SELECT MTINST, MTSFX, MTSRNM, MTGVNM, MTOTHN, MTDATE, MTINTP,
MTSTAT, MTBOOK, MTPAGE, 'mor', RRN(RMSMORPF)FROM RMSMORPF WHERE MTINST >=
50000 ORDER BY 4, 6, 2 FETCH FIRST 100 ROWS ONLY OPTIMIZE FOR 20 ROWS FOR
READ ONLY-->

Bradley V. Stone
BVSTools - www.bvstools.com
eRPG SDK - www.erpgsdk.com

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of
Rick.Chevalier@xxxxxxxxxxxxxxx
Sent: Tuesday, July 08, 2008 1:09 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: SQL and retrieving the next xx rows



Bradley,

Take a look at the FETCH FIRST clause of the select statement. I think
that might be what you are looking for. IIRC there is also a FETCH NEXT
but it requires a cursor.

select.... where ordernum >= searchorder fetch first 100 rows only

HTH,

Rick

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bradley V. Stone
Sent: Tuesday, July 08, 2008 11:00 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: SQL and retrieving the next xx rows

When running an SQL statement on say, and order file, lets say you were
letting the user enter an order number to search by used in the SQL

ie...

Select..... where ordernum = searchorder

Now, lets say that you wanted to also select the next 100 orders after
the order number entered. The problem being that the order numbers are
not sequential.

So we could have:

101
110
111
120
121
122

etc...

So we'd want to say:

select.... where ordernum >= searchorder

but only have it select the next 100 orders (mainly because if we
didn't, the search would take forever if there were a bazillion orders
in the database).

I have seen reference to a LIMIT keyword, but it didn't seem to like it
in the SQL interface.

Thanks!

Bradley V. Stone
BVSTools - www.bvstools.com
eRPG SDK - www.erpgsdk.com