|
From: SourceForge.net <no...@so...> - 2008-08-19 09:21:31
|
intermediateTable not used Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-SourceForge-Tracker-unixname: sqlobject X-SourceForge-Tracker-trackerid: 540672 X-SourceForge-Tracker-itemid: 2059325 X-SourceForge-Tracker-itemstatus: Open X-SourceForge-Tracker-itemassignee: nobody X-SourceForge-Tracker-itemupdate-reason: Tracker Item Submitted X-SourceForge-Tracker-itemupdate-username: Item Submitter Bugs item #2059325, was opened at 2008-08-19 11:21 Message generated for change (Tracker Item Submitted) made by Item Submitter 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: DBM Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Klaus Warnke (kwarnke3) Assigned to: Nobody/Anonymous (nobody) 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=2059325&group_id=74338 |
