[sqlalchemy] Re: New records won't be committed (ORM, Elixir)

2008-02-04 Thread jason kirtland
Felix Schwarz wrote: Thank you very much for your reply - lightning fast as always :-) Gaetan de Menten schrieb: Other than that, maybe you are (or Turbogears is) starting a transaction somewhere (with session.begin()) without ever commiting it? Thanks for your hint. Indeed I used

[sqlalchemy] Re: New records won't be committed (ORM, Elixir)

2008-02-04 Thread Michael Bayer
On Feb 4, 2008, at 8:01 AM, Felix Schwarz wrote: Thank you very much for your reply - lightning fast as always :-) Gaetan de Menten schrieb: Other than that, maybe you are (or Turbogears is) starting a transaction somewhere (with session.begin()) without ever commiting it? Thanks for

[sqlalchemy] Re: New records won't be committed (ORM, Elixir)

2008-02-04 Thread Felix Schwarz
Thank you very much for your reply - lightning fast as always :-) Gaetan de Menten schrieb: Other than that, maybe you are (or Turbogears is) starting a transaction somewhere (with session.begin()) without ever commiting it? Thanks for your hint. Indeed I used session.begin() after my

[sqlalchemy] Re: New records won't be committed (ORM, Elixir)

2008-02-04 Thread Felix Schwarz
jason kirtland wrote: SA won't automatically commit a transaction you've begun. You need to .commit() explicitly. As Michael said, .commit() will flush changes in the session before committing, so you could switch to calling that. It can be useful in a transaction to issue a simple

[sqlalchemy] Re: New records won't be committed (ORM, Elixir)

2008-02-04 Thread Michael Bayer
On Feb 4, 2008, at 4:01 PM, Felix Schwarz wrote: jason kirtland wrote: SA won't automatically commit a transaction you've begun. You need to .commit() explicitly. As Michael said, .commit() will flush changes in the session before committing, so you could switch to calling that.