From time to time I find I need or prefer "dropping into SQL" for
certain tasks, in the midst of making the majority of my database
changes through sqlalchemy's objects; for example, I may use
session.execute(sql).

  I would like these changes to be committed later along with the sqla
session objects *if and only if* the session issues a commit.
However, I've observed that if the *only* database changes were made
via session.execute(), then session.commit() believes there is nothing
to commit, so the "commit" isn't issued to the database.

  Is there a better way to approach what I am trying to accomplish?
Is there a way to tell a session "by the way, you have changes that
you don't know about, so when it comes time to commit, please do so"?

Thanks very much, as always,
Kent

-- 
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.

Reply via email to