patch is attached
--~--~-~--~~~---~--~~
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]
Fo
sorry about the flood...
this should have the limit/offset is None case fixed.
On 15/07/07, lei you <[EMAIL PROTECTED]> wrote:
>
> fixed a bug that exists if limit isn't specified.
>
> things should be fine now...
>
> On 15/07/07, lei you <[EMAIL PRO
fixed a bug that exists if limit isn't specified.
things should be fine now...
On 15/07/07, lei you <[EMAIL PROTECTED]> wrote:
>
> the line
>
> orderby = wrapper.order_by_clause = sql.ClauseList(*map(
> wrapper.corresponding_column, select.order_by_clause.cl
On 15/07/07, lei you <[EMAIL PROTECTED]> wrote:
>
> what is sql generated for the proper fix?
>
> attached is a patch that attempts the wrapper solution. (seems to work for
> both union/non-union selects)
>
> it basically does the following.
>
> wrap the original sele
PROTECTED]> wrote:
>
>
>
>
> On Jul 14, 11:15 pm, "lei you" <[EMAIL PROTECTED]> wrote:
> > # TODO: put a real copy-container on Select and copy, or somehow make
> this
> > # not modify the Select statement
> >
> > In the above comments, are we
/07/07, lei you <[EMAIL PROTECTED]> wrote:
>
> Not exactly sure about what Valentin is doing there, will need to take a
> look at the actual schema and data involved,
>
> select distinct path, row_number() over (order by path desc) as ora_rn
> from Block
>
> row_number()
(select distinct path
from Block)
On 14/07/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
>
>
> On Jul 13, 2007, at 4:20 AM, lei you wrote:
>
> > Thank you for the extremely speedy response :)
> >
> > Are we aware of any other impacts of oracle's offset+l
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
Patch is attached again
--~--~-~--~~~---~--~~
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 PROTECT
