]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
force uselist=False for all collection class not present
authorMike Bayer <mike_mp@zzzcomputing.com>
Tue, 2 Jan 2024 16:36:20 +0000 (11:36 -0500)
committerMike Bayer <mike_mp@zzzcomputing.com>
Tue, 2 Jan 2024 17:02:18 +0000 (12:02 -0500)
commit2ce6010c924e963dcd9245b99e583611be5fb061
treef9be16c6fcd1f3e248d5879c30c656f0872cf073
parenta7f98b4eb88382ccb671857f62e560d5d35c81ab
force uselist=False for all collection class not present

Fixed issue where ORM Annotated Declarative would mis-interpret the left
hand side of a relationship without any collection specified as
uselist=True if the left type were given as a class and not a string,
without using future-style annotations.

Fixes: #10815
Change-Id: I85daccec03f7e6ea3b49eb07c06e0f85e361a1c0
(cherry picked from commit c1139c2e5d2f14738798d3c0deb876286014c808)
doc/build/changelog/unreleased_20/10815.rst [new file with mode: 0644]
lib/sqlalchemy/orm/relationships.py
test/orm/declarative/test_tm_future_annotations_sync.py
test/orm/declarative/test_typed_mapping.py