Ive added ticket #759 for this and I think before 0.4 is finalized, I'll be working out the full "solution" for Postgres inserts/updates, which will allow a flag "inline=True" on all Insert/Update constructs indicating that all SQL expressions should execute "inline" (i.e. no pre-execution), and I'll also make it more intelligent about PG in this case (i.e. where SERIAL can autoincrement the sequence for you, dont render any literal sequence expression at all). "inline=True" will also take effect automatically for all executemany() scenarios since the "pre-execute" thing there is totally wasteful. (the pre- execution logic is primarily so we can get the row's ID in the case of a sequence-oriented database, which includes postgres, oracle and firebird).
On Aug 27, 2007, at 2:44 AM, che wrote: > > Thanks Michael, > > it is not urgent to me. if i found time i'll look down what is causing > this and eventually try to patch. > > regards, > stefan > > On 25 Авг, 03:09, Michael Bayer <[EMAIL PROTECTED]> wrote: >> On Aug 23, 2007, at 11:18 AM, che wrote: > >> >> i cant reply to this issue for another week since im out of town. as >> a workaround, placing "autoincrement=False" on your primary key >> column for now may resolve the issue. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
