Anssi Kääriäinen aa22cbd51a Fixed #20583 -- ORM always uses setup_joins() for join generation ... There were a couple of places which used Query.join() directly. By using setup_joins() in these places the code is more DRY, and in addition there is no need to directly call field.get_joining_columns() unless the field is the given join_field from get_path_info(). This makes it easier to make sure a ForeignObject subclass generates joins correctly in all cases.		2013-06-16 15:44:52 +03:00
..
__init__.py	Remove all relative imports. We have always been at war with relative imports.	2011-10-18 00:47:49 +00:00
aggregates.py	Replaced `and...or...` constructs with PEP 308 conditional expressions.	2013-05-26 23:47:50 -03:00
compiler.py	Fixed #20583 -- ORM always uses setup_joins() for join generation	2013-06-16 15:44:52 +03:00
constants.py	Fixed #19385 again, now with real code changes	2013-03-24 18:40:40 +02:00
datastructures.py	Fixed #19964 -- Removed relabel_aliases from some structs	2013-03-12 21:33:47 +02:00
expressions.py	Fixed #19385 again, now with real code changes	2013-03-24 18:40:40 +02:00
query.py	Fixed #20583 -- ORM always uses setup_joins() for join generation	2013-06-16 15:44:52 +03:00
subqueries.py	Replaced an antiquated pattern.	2013-05-17 18:08:58 +02:00
where.py	Fixed #20507 -- SubqueryConstraint alias relabeling	2013-05-27 12:25:29 +03:00