You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by "Thomas Fischer (JIRA)" <ji...@apache.org> on 2006/10/17 08:58:36 UTC
[jira] Resolved: (TORQUE-10) doSelectJoinYYY in Oracle fails with
limit/offset and same column names
[ http://issues.apache.org/jira/browse/TORQUE-10?page=all ]
Thomas Fischer resolved TORQUE-10.
----------------------------------
Fix Version/s: 3.2.1
Resolution: Fixed
Assignee: Thomas Fischer
Was fixed by automatically aliasing one of the duplicate columns.
> doSelectJoinYYY in Oracle fails with limit/offset and same column names
> ------------------------------------------------------------------------
>
> Key: TORQUE-10
> URL: http://issues.apache.org/jira/browse/TORQUE-10
> Project: Torque
> Issue Type: Bug
> Components: Runtime
> Affects Versions: 3.2
> Environment: Oracle
> Reporter: Thomas Fischer
> Assigned To: Thomas Fischer
> Fix For: 3.2.1
>
>
> Reported by Bouvet Konsulent: If a criteria with a limit or Offset is used in XXXPeer.doSelectJoinYYY(Criteria), and the Tables XXX and YYY have columns with same names, the method fails with a ORA-00918: column ambiguously defined.
> This is because the "select *" from the limit/offset query clashes with the two same names in the inner select clause.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org