|
From: SourceForge.net <no...@so...> - 2009-09-08 18:05:16
|
Bugs item #2059325, was opened at 2008-08-19 13:21 Message generated for change (Settings changed) made by phd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=2059325&group_id=74338 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General Group: None >Status: Closed >Resolution: Wont Fix Priority: 5 Private: No Submitted By: Klaus Warnke (kwarnke3) Assigned to: Oleg Broytmann (phd) Summary: SQLRelatedJoin: defaultOrder of intermediateTable not used Initial Comment: The SELECT build for a SQLRelatedJoin does not use the sqlmeta: defaultOrder from the intermediateTable. This is not urgent, because I can provide an orderBy in to the join constructor, but it would by nice if it works automatic. Btw: The documentation seems to be outdated, because the _defaultOrder class variable was replaced with class sqlmeta: defaultOrder I think. And what is about defaultOrderBy I have seen in a test_combining_joins.py? ---------------------------------------------------------------------- Comment By: Oleg Broytmann (phd) Date: 2009-04-29 18:20 Message: SQLRelatedJoin uses defaultOrder from the other table, but not from the intermediate table: if self.orderBy is NoDefault: self.orderBy = self.otherClass.sqlmeta.defaultOrder Do you want SQLObject to test the order of the other table then from the intermediate table and to use the first one that is not None? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=2059325&group_id=74338 |
