I think my issue is that before the commit/rollback
Alice.id is None but after Alice.id is set to some integer. I understand the 
object is transient but I wish that the primary key field was not modified in 
this way because if I want to try to reinsert Alice in a new transaction I have 
to write logic to introspect into the schema and unset the primary key. This 
behavior also breaks my mental model of “the object is the way it was before 
the commit failure and rollback”.

-- 
SQLAlchemy - 
The Python SQL Toolkit and Object Relational Mapper

http://www.sqlalchemy.org/

To post example code, please provide an MCVE: Minimal, Complete, and Verifiable 
Example.  See  http://stackoverflow.com/help/mcve for a full description.
--- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

Reply via email to