Hi All,
Is it legit/okay/bad to do things in a MapperExtension's before_insert
and/or before_update methods?
Specifically, the following:
- change the primary key of the instance by deleting it so that the
dataabse assigns a new primary key?
- do a query to update an existing row? (where would I get the session
from?)
- change the row the instance corresponds to and somewhow return a "new
replacement instance"?
(and yes, this post is related to the versioning post I sent this morning.)
I've read the versioning example includes in SA, but unfortunately I
couldn't grok how I'd say "gimme the version of this object as it was on
5pm last Tuesday". Was I missing something there?
cheers,
Chris
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
