The problem is that ROW_NUMBER() is not based on the result set defined by
the where clause - but rather base input data set...
My gues is that rows from 21 to 40 in the physical file does not contain any
thing with "Brooks"
For that kind of cursors I suggest that you rather use "scrolling cursors"
where you can give the starting row number as a parameter for the fetch
(don?t know If that is supported in the PNP toolbox yet btw.)
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Burke, Joel
Sent: 20. oktober 2008 20:14
To: web400@xxxxxxxxxxxx
Subject: [WEB400] sql in php with paging
I have written a php script that displays a list of individuals. The script
uses paging with 20 results per screen and searching is allowed on the name
field or id number. I am having an issue coding a case insensitive search.
Here is an example of my sql that works but is not case insensitive:
SELECT * FROM (SELECT ROW_NUMBER() OVER(order by name) AS rownum, id, name,
address, city, state, zip FROM testlib.mastfile where (name like '%Brooks%'
or id = 0)) AS col WHERE rownum BETWEEN 21 and 40
The above code gives me records 21-40 based on the selection and sort. Here
is how I changed the code to allow for case insensitive searching:
SELECT * FROM (SELECT ROW_NUMBER() OVER(order by name) AS rownum, id, name,
address, city, state, zip FROM testlib.mastfile where (upper(name) like
upper('%Brooks%') or id = 0)) AS col WHERE rownum BETWEEN 21 and 40
I do not receive any results back from the code above. I have testes the
following and it works properly:
SELECT * from testlib.mastfile where upper(name) like upper('%brooks%')
Any idea what I am doing wrong? I am fairly new to sql so I may just be
overlooking the obvious.
TIA
Joel
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.