[ http://issues.apache.org/jira/browse/TORQUE-34?page=all ]
Thomas Fischer resolved TORQUE-34:
----------------------------------
Fix Version: 3.2
Resolution: Fixed
Assign To: Thomas Fischer
I cannot reproduce this in 3.2.1-dev, so I believe it has been fixed in 3.2
where SQL generation was mixed up a good deal. I added a test case to the
CriteriaTest in rutime to check this.
Alias'ed table names are added as alias.column from the order by if they are
added (they are added only for strings, no idea why this is the case).
If the issue still persists, please reopen this issue and provide code to
create the sql in question, the produced sql, and the sql as you think it
should be.
> OrderBy using alias's and multiple tables causes error on Sybase ASE 12.5
> -------------------------------------------------------------------------
>
> Key: TORQUE-34
> URL: http://issues.apache.org/jira/browse/TORQUE-34
> Project: Torque
> Type: Bug
> Components: Runtime
> Environment: Sybase ASE 12.5
> Reporter: Scott Eade
> Assignee: Thomas Fischer
> Fix For: 3.2
>
> When I include an OrderBy on a Criteria that uses table alias's, the order by
> column is added to the select clause as TableName.Column, not alias.Column.
> This results in an error on Sybase ASE 12.5 - you cannot reference a column
> by TableName if an alias is defined. Removing line 1281-82 from BasePeer from
> v3.1 solves this issue for Sybase, but I don't know what affect it has on
> other databases
> Scarab issue was raised by Jimmy Myerscough (wumpus at earthling dot net).
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
