Assigning SQL expression to a version column.

[Jeff Horemans]

What is the expected behavior of assigning an SQL expression to a version column?

Before migrating from version 1.2.4. to 1.3.3. the priority was given to the assigned expression, afterwards it seems to be the other way around.

I think there is something to say about both, but I wanted to check if this change was purposely done and what the reasoning is going forward.

Thanks in advance.

[Mike Bayer]

There is no test coverage and as far as I can see at the moment no documentation for such a use case as of yet, and per the documentation at https://docs.sqlalchemy.org/en/13/orm/versioning.html?highlight=versioning#programmatic-or-conditional-version-counters, unless I am missing something, programmatic assignment of the version id is only valid when the generator is False, that is, there is no defined or supported behavior in SQLAlchemy for the case where an automatic version counter is configured and the application may sporadically assign an explicit vresion counter with the purpose of overriding that value.

I'm only going by your verbal description however so if we are to create a behavioral definition here this would usually happen via github issues that illustrate a complete MCVE [1]

[1] http://stackoverflow.com/help/mcve

--

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+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy/990ee6f0-76f7-4c28-abe2-23de1a866ce6%40googlegroups.com.