From da04aa577b6e539a6472df62ee39c4a51cca9dd9 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Sat, 23 Mar 2019 22:05:22 -0400 Subject: Fix boolean check in new path comparison logic Fixed regression where a new error message that was supposed to raise when attempting to link a relationship option to an AliasedClass without using :meth:`.PropComparator.of_type` would instead raise an ``AttributeError``. Note that in 1.3, it is no longer valid to create an option path from a plain mapper relationship to an :class:`.AliasedClass` without using :meth:`.PropComparator.of_type`. Fixes: #4566 Change-Id: Ic547a1c8408e41aec66ef9644aac7f76f50dd064 --- doc/build/changelog/unreleased_13/4566.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/build/changelog/unreleased_13/4566.rst (limited to 'doc') diff --git a/doc/build/changelog/unreleased_13/4566.rst b/doc/build/changelog/unreleased_13/4566.rst new file mode 100644 index 000000000..3fb1a49e8 --- /dev/null +++ b/doc/build/changelog/unreleased_13/4566.rst @@ -0,0 +1,10 @@ +.. change:: + :tags: bug, orm + :tickets: 4566 + + Fixed regression where a new error message that was supposed to raise when + attempting to link a relationship option to an AliasedClass without using + :meth:`.PropComparator.of_type` would instead raise an ``AttributeError``. + Note that in 1.3, it is no longer valid to create an option path from a + plain mapper relationship to an :class:`.AliasedClass` without using + :meth:`.PropComparator.of_type`. -- cgit v1.2.1