the query generated by subquery when using filters unambiguously labeling columns resulting in an ambiguous column exception.
long story short, I have a polymorphic database, so id is shared between a base class and the filtered child class. that seems to be the root of the issue. after playing around for a while I found subquery.subquery() has a with_labels argument you can pass. setting that to True fixed the issue for me
hey @art1415926535 can you look at this and/or add this? I don't want to make another forked library to maintain and this simple change fixes a critical issue and should cause no side effects
the query generated by subquery when using filters unambiguously labeling columns resulting in an ambiguous column exception.
long story short, I have a polymorphic database, so id is shared between a base class and the filtered child class. that seems to be the root of the issue. after playing around for a while I found subquery.subquery() has a with_labels argument you can pass. setting that to True fixed the issue for me
e.g. connection_field.py line 250