Gaetan de Menten wrote: > As far as I remember, SQLAlchemy handles the column all by itself, > so there might be a problem indeed.
Indeed, it appears that you are correct. I asked this question over on the SQLAlchemy list, and got back the following response from Mike: > 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. So, my patch totally won't work properly right now. I'll have to go back to the drawing board here. It appears to me that the easiest thing to do would be to simply add an additional "concurrency_version" column, and let both elixir and SQLAlchemy do their own thing, as I don't think we can just hand over the version column to SQLAlchemy... What do you think? -- Jonathan LaCour http://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLElixir" 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/sqlelixir?hl=en -~----------~----~----~----~------~----~------~--~---
