- changed status to duplicate
changing a relation from lazy to dynamic generates incorrect SQL
Issue #1530
resolved
Firstly. Fantastic software guys! Here's the problem: changing lazy=True to lazy='dynamic' on an orm.relation function with a 'secondary_join' and an 'order_by' filter results in broken SQL. Essentially the secondary table is aliased in the SQL but the order_by reference to the secondary is not. I have a small program that exhibits the problem on a MySQL database.
Comments (1)
-
Account Deleted - Log in to comment
(original author: ged) dupe of
#1531