Re: Can an SQL common table expression be used for many different selects? -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Thank you , Maria. This is the part I still don't understand, but I guess the row_number() function is a little more intelligent than I thought. As long as it works for you, that's great! Like you, I'll do more investigation when I have some extra time.

On 8/4/2020 10:59 AM, Maria Lucia Stoppa wrote:

Slightly different: the first select creates 1000 rows in the static key
table, then when my first pagination selects 50 rows, the first one is
numbered 1000, the second one 999, the third one 998 and so on and on.
So the first row gives me the total number of selected rows, no matter what
pagination is in use.
Is it clearer?

Il giorno mar 4 ago 2020 alle ore 17:16 Joe Pluta <
joepluta@xxxxxxxxxxxxxxxxx> ha scritto:

Let me see if I understand. Let's assume the first select creates 1000
rows in the static keys table, and then your first pagination selects
only 50 of those rows. In that case, the first row from the pagination
select would have a row_number of 50, the second would have 49 and so
on, correct?

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.