Thank you for the extremely speedy response :) Are we aware of any other impacts of oracle's offset+limit implication?
On 13/07/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > > On Jul 13, 2007, at 4:07 AM, Esceo wrote: > > > > > Hi all, > > > > attached is an experimental patch for mssql.py merged with r2891: > > > > this is a direct steal from the oracle implementation of limit + > > offset using row_number() > > > > what I would like to find out are the following: > > > > the oracle implementation has visit_compound_select marked as todo, > > what is the implication of that? (my guess is that limit+offset won't > > work for join models?) > > visit_compound_select is for unions. most times when we use unions > with the ORM, an enclosing select is issued around the UNIONs so it > doesnt matter. joins are OK. > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
