[Sqlalchemy-tickets] Issue #3238: When using m2m association collections, strange behavior occurs, if the session is not committed. (zzzeek/sqlalchemy)

[Boris K. <iss...@bi...>]

New issue 3238: When using m2m association collections, strange behavior occurs, if the session is not committed.
https://bitbucket.org/zzzeek/sqlalchemy/issue/3238/when-using-m2m-association-collections

Boris Kozinsky:


If the session is not committed:
When appending to collection the association object is not created.
When the association object is created, the collection is not updated.

If the session is committed:
Both association objects and collections are updated, but using difference routes it seems, which is reflected in the way object initialization is happening.

Is this normal? I would think that the results should not depend on whether the session is committed to the database. This would be much easier for testing, if everything was updated and available for querying even without a commit.

Note: in the attached file the association table UserKeywords has an extra field (special_key), but that is not relevant for this report.