On Dec 30, 2007, at 5:49 PM, jerryji wrote:
>
> The missing commit() is the culprit! Thanks so much Alex.
>
> It has been a little deceiving as commit() doesn't seem to be required
> for calling execute() on select statements
>
> Sincerely,
> Jerry
>
one thing thats tricky here is that if you weren't using a
transaction, SQLAlchemy normally issues "autocommit" behavior based on
the SQL that was issued. it checks for INSERT/UPDATE/DELETE etc. to
determine if COMMIT is required...so in the case of a SELECT which
changes things, youd have to issue it inside of a BEGIN/COMMIT to have
the commit occur. This is a slight shortcoming in SA"s API which we
eventually need to address, using something like text("select * from
table", should_commit=True). I just added ticket 915 to discuss that.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
