Return-Path: Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm Delivered-To: mailing list torque-user@db.apache.org Received: (qmail 26596 invoked from network); 10 Mar 2003 08:36:44 -0000 Received: from wrath.forked.net (216.65.131.190) by daedalus.apache.org with SMTP; 10 Mar 2003 08:36:44 -0000 Received: from wrath.forked.net (IDENT:fredgers@localhost [127.0.0.1]) by wrath.forked.net (8.12.6/8.12.6) with ESMTP id h2A8WJgY015768 for ; Mon, 10 Mar 2003 00:32:19 -0800 Received: from localhost (fredgers@localhost) by wrath.forked.net (8.12.6/8.12.6/Submit) with ESMTP id h2A8WJWw015765 for ; Mon, 10 Mar 2003 00:32:19 -0800 Date: Mon, 10 Mar 2003 00:32:19 -0800 (PST) From: Fred Gerson To: torque-user@db.apache.org Subject: order by column problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hey All, I'm porting an app from Turbine 2.1 to Turbine 2.2 and I'm having trouble with the Criteria object's addAscendingOrderByColumn() method. I have the below code that worked fine in 2.1 but now breaks in 2.2 Criteria criteria = new Criteria(); criteria.addAscendingOrderByColumn(AffinityinfoPeer.CYCLE); criteria.addAscendingOrderByColumn(AffinityinfoPeer.CLIENTNUMBER); return AffinityinfoPeer.doSelect(criteria); The doSelect() method above works fine if I comment out the two orderBy lines above it. The doSelect() method will also work fine if I just do a criteria.add(column, someValue) with the two columns above and no ordering. However when I call addAscendingOrderByColumn for some reason this kills the criteria object - calling toString() on the criteria object returns a string with no SQL in it. Has anyone else had trouble with this method in Torque 3.0? Am I overlooking something silly? Please Help. Thanks, Fred