On Nov 20, 7:39 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> On Nov 20, 2008, at 9:05 PM, bukzor wrote:
>
> > Would it make sense to rename Insert.values to Insert.params? Or make
> > Insert.params call Insert.values.
> > It seems quite strange for an object to have functions that aren't
> > usable...
>
> its an entirely different function. If you said this:
>
> t = table.update().where(table.c.col1==bindparam('x', value=5))
>
> Saying this:
>
> t2 = t.params('x', 12)
>
> would in theory produce (with bind values inlined) UPDATE table WHERE
> x=12
>
> while saying this:
>
> t3 = t.values('x', 12)
>
> would produce UPDATE TABLE SET x=12 WHERE x=5
>
> for an INSERT, the difference would apply to bind params that are
> perhaps embedded in subqueries within the VALUES clause.
>
Thanks for explaining. My problem was that I thought the insert values
would be implemented as bindparams.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
