Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Users List" <torque-user@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of helgew@grajagan.org
 designates 66.159.194.18 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <0CE15DD3-C317-4A90-8747-265991AFFF68@grajagan.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: Apache Torque Users List <torque-user@db.apache.org>
From: Helge Weissig <helgew@grajagan.org>
Subject: Criteria.addAsColumn and
 Criteria.add{Ascending,Descending}OrderByColumn not compatible?
Date: Fri, 7 Sep 2007 10:58:15 -0700

Hi there,

	I found a message in the archives dated sometime in 2003 that  
described the exact same problem I am having: if you add an alias for  
a column with Criteria.addAsColumn(), you cannot use it as a  
orderByColumn using Criteria.addAscendingOrderByColumn() or  
Criteria.addDescendingOrderByColumn() because somewhere a  
table_name.COLUMN_NAME format is enforced and a TorqueException is  
thrown. FWIW, a fix/patch was also reported: http://mail- 
archives.apache.org/mod_mbox/db-torque-user/200310.mbox/% 
3cB0EC737D3663D411868C00D0B77A8BC49DC254@nt_exchange%3e

Are there any plans of addressing this? If not, what is the process  
of providing patches? Last not least, did anyone come up with a  
different work-around? FWIW, we are using the 3.2 RC1 tagged code  
from the svn repository.

thanks,
h.

---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org