Re: [sqlalchemy] Extending mapper to use PostgreSQL's INSERT/UPDATE...RETURNING

2009-12-23 Thread Michael Bayer
Igor Katson wrote: >> > Thanks, Michael, it's clear now. A was not thinking that Python's > overhead might be more than RDBMS's one. After profiling my application > with repoze.profile and apache ab, I see that SQL only takes around 10% > of the request serving time (being extremely fast and serv

Re: [sqlalchemy] Extending mapper to use PostgreSQL's INSERT/UPDATE...RETURNING

2009-12-23 Thread Igor Katson
Michael Bayer wrote: > On Dec 22, 2009, at 5:20 PM, Igor Katson wrote: > >>> 0.5 supports this using the "postgres_returning" argument to update() and >>> insert(), but the ORM doesn't make use of it. in 0.6, the feature has been >>> generalized using the returning() method on insert() and upda

Re: [sqlalchemy] Extending mapper to use PostgreSQL's INSERT/UPDATE...RETURNING

2009-12-22 Thread Michael Bayer
On Dec 22, 2009, at 5:20 PM, Igor Katson wrote: >> 0.5 supports this using the "postgres_returning" argument to update() and >> insert(), but the ORM doesn't make use of it. in 0.6, the feature has been >> generalized using the returning() method on insert() and update(), and the >> ORM will

Re: [sqlalchemy] Extending mapper to use PostgreSQL's INSERT/UPDATE...RETURNING

2009-12-22 Thread Michael Bayer
On Dec 22, 2009, at 2:51 PM, Igor Katson wrote: > > I am concerned about the problem of the orm framework using SELECT's a > lot, which can be not used in many cases, when dealing with Postgres > after INSERTs or UPDATEs. on this point specifically, when a SQL expression is used to generate t

Re: [sqlalchemy] Extending mapper to use PostgreSQL's INSERT/UPDATE...RETURNING

2009-12-22 Thread Igor Katson
Michael Bayer wrote: > On Dec 22, 2009, at 2:51 PM, Igor Katson wrote: > > >> I am concerned about the problem of the orm framework using SELECT's a >> lot, which can be not used in many cases, when dealing with Postgres >> after INSERTs or UPDATEs. >> >> When using postgresql, I want sqlalche

Re: [sqlalchemy] Extending mapper to use PostgreSQL's INSERT/UPDATE...RETURNING

2009-12-22 Thread Michael Bayer
On Dec 22, 2009, at 2:51 PM, Igor Katson wrote: > > I am concerned about the problem of the orm framework using SELECT's a > lot, which can be not used in many cases, when dealing with Postgres > after INSERTs or UPDATEs. > > When using postgresql, I want sqlalchemy, when updating the instanc

[sqlalchemy] Extending mapper to use PostgreSQL's INSERT/UPDATE...RETURNING

2009-12-22 Thread Igor Katson
Hi, when I started using code like obj.column = obj.column + 1, which I had to make through raw sql (because in SQL e.g. "update...set column = 400 + 1" is not equal to "update...set column = column + 1", when many threads do this concurrently), I faced a problem, that to update the value and