On Feb 14, 2008, at 10:19 AM, Jonathan LaCour wrote:
I'd like to automatically enable the SQLAlchemy concurrent
modification checking on versioned mappers using the
`version_id_col` argument, but the documentation isn't clear on
how it works. Is this column managed by SQLAlchemy or is it to be
managed by the user? Since our existing version column is managed
by Elixir itself, I need to know if I can use it as the argument to
`version_id_col` without SQLAlchemy and Elixir conflicting in who
controls the column.
its managed entirely by SQLAlchemy at the moment, starts at 1 and
increments automatically, and acutually doesnt have any connection to
class-based attributes so its a little insular. I would think that
elixir could just move its own management of the version over to this
mechanism but we can also look into opening up its behavior if that
suits your functionality better.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
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
-~--~~~~--~~--~--~---
