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: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: ORDER BY and torque generated column names
Date: Mon, 6 Oct 2008 10:11:58 -0700
Message-ID: <C27EE712DBADE14286DA449499F17F8794F1D8@ABmail.activx.com>
In-Reply-To: <48EA01BC.3030103@sharp.fm>
Thread-Topic: ORDER BY and torque generated column names
thread-index: Acknrb1Z5O5iHEl4SSe2hTmoNnG+awAKHbVw
From: "Manaster, Carl" <CarlM@ACTIVX.com>
To: "Apache Torque Users List" <torque-user@db.apache.org>

Hi, Graham,

> Am I doing something wrong in the following code?
>=20
> criteria.addJoin(BPeer.POLICYDETAIL_ID,=20
> APeer.POLICYDETAIL_ID);=20
> criteria.addDescendingOrderByColumn(BPeer.UNDERWRITING_YEAR);
> criteria.addDescendingOrderByColumn(APeer.POLICYDETAIL_ID);
> APeer.doSelect(criteria);

I think the issue is that when you ask APeer to select, it will select
only the fields from a; it's telling you that you can't ORDER BY
b.underwriting_year because that is not one of the columns in a.  You
could specify with addSelectColumn() exactly which columns you want to
select and use BasePeer.doSelect() instead of APeer.doSelect, but that
will give you com.workingdogs.village Records rather than a's, if that
matters.

Peace,
--Carl

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