[sqlalchemy] Re: not expected generated update query values

2009-11-04 Thread Michael Bayer
sector119 wrote: > > Oh, I forgot about that, it wasn't that behaviour that I realy > axpect.. > I modify sql/compiller.py a bit to show what I mean. If I specify some > bindparam'eters at value(...) I want _only_ that columns to be at > update SET or insert VALUES.. > > --- compiler.py.orig20

[sqlalchemy] Re: not expected generated update query values

2009-11-04 Thread sector119
Oh, I forgot about that, it wasn't that behaviour that I realy axpect.. I modify sql/compiller.py a bit to show what I mean. If I specify some bindparam'eters at value(...) I want _only_ that columns to be at update SET or insert VALUES.. --- compiler.py.orig2009-11-02 18:00:17.548954070 +020

[sqlalchemy] Re: not expected generated update query values

2009-10-23 Thread sector119
Thanks a lot, Michael! On Oct 23, 4:09 am, Michael Bayer wrote: > On Oct 22, 2009, at 3:26 PM, sector119 wrote: > > > > > Something strange, Michael.. All bindparams are different. Compliller > > should not add to SET all params if values() has bindparam args, no? > > where() have: > >    bindpa

[sqlalchemy] Re: not expected generated update query values

2009-10-22 Thread Michael Bayer
On Oct 22, 2009, at 3:26 PM, sector119 wrote: > > Something strange, Michael.. All bindparams are different. Compliller > should not add to SET all params if values() has bindparam args, no? > where() have: >bindparam('commit_date'), bindparam('serial'), bindparam > ('office_id') > values()

[sqlalchemy] Re: not expected generated update query values

2009-10-22 Thread Michael Bayer
sector119 wrote: > > Something strange, Michael.. All bindparams are different. Compliller > should not add to SET all params if values() has bindparam args, no? > where() have: > bindparam('commit_date'), bindparam('serial'), bindparam > ('office_id') > values() have: > bindparam('rollbac

[sqlalchemy] Re: not expected generated update query values

2009-10-22 Thread sector119
Something strange, Michael.. All bindparams are different. Compliller should not add to SET all params if values() has bindparam args, no? where() have: bindparam('commit_date'), bindparam('serial'), bindparam ('office_id') values() have: bindparam('rollback_date'), bindparam('rollback_tim

[sqlalchemy] Re: not expected generated update query values

2009-10-22 Thread Michael Bayer
sector119 wrote: > >> though likely cleaner to pass the exact set of parameters desired. > > How to pass that params if I use bindparam at where() and values(), > but I don't want to update colums that are at where() clause, only at > values() ? if you are using bindparam() objects, you'd given t

[sqlalchemy] Re: not expected generated update query values

2009-10-22 Thread sector119
> though likely cleaner to pass the exact set of parameters desired. How to pass that params if I use bindparam at where() and values(), but I don't want to update colums that are at where() clause, only at values() ? --~--~-~--~~~---~--~~ You received this message

[sqlalchemy] Re: not expected generated update query values

2009-10-22 Thread Michael Bayer
sector119 wrote: > > Hi All! > > Why I get at SET part not only items from values(...), but all from > params passed to session.execute? > transactions_update = model.transactions_table.update().where(and_(model.transactions_table.c.commit_date==bindparam('commit_date'), model.trans