Thanks. Charles provided a similar statement earlier. And I get the CTE works.
But I'm still curious that the row_number function works differently based on the 'order by' clause. Charles mentioned earlier that he suspects the regExp_like is the culprit, but regExp_like is in the statement that numbers only the resulting records and it is in the statement that numbers the records before applying the 'where' clause.
If someone can provide an explanation, I'm listening. Otherwise, I've moved on with the CTE.
Thanks to the mailing list for everyone's help
-----Original Message-----
From: Jack Callahan <jjcllhn@xxxxxxxxx>
To: midrange-l <midrange-l@xxxxxxxxxxxx>
Sent: Fri, Nov 30, 2018 8:41 am
Subject: RE: row_number ignores where clause w/ order by
I think this works the way you expect (row numbers assigned by descending
size for the selected tables:
With SelectTables AS
(select *
from qSys2.sysTableStat
where regExp_like( table_schema, 'JJCWORK' )
order by data_size desc
)
SELECT row_number() over(order by data_size desc) as rowNumber,s.* from
SelectTables s;
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: row_number ignores where clause w/ order by, (continued)
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.