> > Note that if you use ROWNO, then a following ORDER BY clause will sort > > only > > the records until the limit of ROWNO is reached. It says so in the manual > > at > > least, I haven't tried it... Makes the feature a bit useless IMO... You > > can > > set MaxDB to parse in Oracle mode and use ROWNUM to limit/offset.. > >
> ??? What do you change when using Oracle mode and ROWNUM instead of internal mode and ROWNO? NOTHING > And even Oracle (9i) only sorts the first ROWNO results, the same as MaxDB. Are you saying that ROWNO can be used to offset as well, not only to limit? Like Oracle can do "... WHERE ROWNUM > 10" ? If so, the documentation does not reflect that. > Perhaps one should point out that the ROWNO/ROWNUM is to limit the > select-work needed to select the wanted number of rows. And if you want to > receive the first x ORDERED rows, then ALL rows would be needed for > selection, then ordering and then thrown away (most of them). That would > make no sense. So are you saying that returning for example 1,000 sorted results or just 10 out of 1,000 sorted records (assuming ROWNO would be able to sort all 1,000 records and return the first 10 after sorting) does not make any difference in performance/memory usage on the client side and in MaxDB? Maybe cursor handling is the way to go, but I haven't figured out a way to do so, thanks to cryptic manuals and lack of tutorials. Maybe someone could help the ignorant a bit and put up a simple tutorial how to fetch rows with cursors. I bet most people coming from MySQL will have a hard time with that. (if you care about this audience). Best wishes -Zavier -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
