Return-Path: 
 <ojb-dev-return-12857-apmail-db-ojb-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-ojb-dev-archive@www.apache.org
Received: (qmail 96976 invoked from network); 20 Oct 2005 13:31:24 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 20 Oct 2005 13:31:24 -0000
Received: (qmail 58906 invoked by uid 500); 20 Oct 2005 13:31:23 -0000
Delivered-To: apmail-db-ojb-dev-archive@db.apache.org
Received: (qmail 58871 invoked by uid 500); 20 Oct 2005 13:31:23 -0000
Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ojb-dev-unsubscribe@db.apache.org>
List-Help: <mailto:ojb-dev-help@db.apache.org>
List-Post: <mailto:ojb-dev@db.apache.org>
List-Id: "OJB Developers List" <ojb-dev.db.apache.org>
Reply-To: "OJB Developers List" <ojb-dev@db.apache.org>
Delivered-To: mailing list ojb-dev@db.apache.org
Received: (qmail 58860 invoked by uid 99); 20 Oct 2005 13:31:23 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Oct 2005 06:31:23 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [198.234.141.154] (HELO rhocl001.odn.state.oh.us)
 (198.234.141.154)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Oct 2005 06:31:22 -0700
Received: from soccemfe02.em.ohio.gov (soccemfe02.em.ohio.gov [156.63.64.186])
	by rhocl001.odn.state.oh.us (Switch-3.1.6/Switch-3.1.6) with ESMTP id
 j9KDUxZC3448836
	for <ojb-dev@db.apache.org>; Thu, 20 Oct 2005 09:31:00 -0400
Received: from ODNEXCH2.em.ohio.gov ([156.63.64.172]) by
 soccemfe02.em.ohio.gov with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 20 Oct 2005 09:30:59 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [jira] Created: (OJB-75) orderby attribute in repository_user.xml
 not always respected
Date: Thu, 20 Oct 2005 09:30:59 -0400
Message-ID: <41C2B90B26CA6343A75BF031D9A44E12011EB8C7@ODNEXCH2.em.ohio.gov>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [jira] Created: (OJB-75) orderby attribute in
 repository_user.xml not always respected
Thread-Index: AcXUaylxpFqavyyFRUW6crMQtNA7iQBD0plQ
From: "Clute, Andrew" <Andrew.Clute@etech.ohio.gov>
To: "OJB Developers List" <ojb-dev@db.apache.org>
X-OriginalArrivalTime: 20 Oct 2005 13:30:59.0733 (UTC)
 FILETIME=[82378450:01C5D57A]
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

This is fixed in 1.0.4

Collection Prefetcher was not respecting order-by's.

-Andrew

=20

> -----Original Message-----
> From: Al Lofus (JIRA) [mailto:jira@apache.org]=20
> Sent: Tuesday, October 18, 2005 8:37 PM
> To: ojb-dev@db.apache.org
> Subject: [jira] Created: (OJB-75) orderby attribute in=20
> repository_user.xml not always respected
>=20
> orderby attribute in repository_user.xml not always respected
> -------------------------------------------------------------
>=20
>          Key: OJB-75
>          URL: http://issues.apache.org/jira/browse/OJB-75
>      Project: OJB
>         Type: Bug
>   Components: PB-API =20
>     Versions: 1.0.3   =20
>  Environment: All
>     Reporter: Al Lofus
>=20
>=20
> We have an object mapping defined that contains a=20
> collection-descriptor. That collection-descriptor uses an=20
> orderby attribute and an indirection table, as follows:
>=20
> <class-descriptor=20
> class=3D"com.dchoc.common.entity.LeagueEntity" table=3D"LEAGUES">
>     <field-descriptor id=3D"1" name=3D"id" column=3D"ID"=20
> jdbc-type=3D"INTEGER" primarykey=3D"true" autoincrement=3D"true"/>
>     <field-descriptor id=3D"2" name=3D"name" column=3D"NAME"=20
> jdbc-type=3D"VARCHAR"/>
>     <collection-descriptor
>      name=3D"members"
>      auto-retrieve=3D"true"
>      auto-update=3D"object"
>      auto-delete=3D"object"
>      proxy=3D"true"
>      indirection-table=3D"LEAGUE_MEMBERS"
>      orderby=3D"leagueSequence"
>      =
element-class-ref=3D"com.dchoc.common.entity.LeagueAccountEntity">
> 	<fk-pointing-to-this-class column=3D"LEAGUE_ID"/>
>      	<fk-pointing-to-element-class column=3D"LEAGUE_ACCOUNT_ID"/>
>     </collection-descriptor>
> </class-descriptor>
>=20
> We were having problems where sometimes the objects returned=20
> in the members collection were ordered by the leagueSequence,=20
> and sometimes they weren't. From our testing, we determined=20
> that the objects in the members collection were ordered by=20
> leagueSequence when the LeagueEntity objects were obtained=20
> via a call to PersistenceBroker.getObjectByQuery(Query). When=20
> the LeagueEntity objects were obtained via a call to=20
> PersistenceBroker.getCollectionByQuery(Query), the objects in=20
> the members collection were *not* ordered by leagueSequence=20
> (they were ordered by a default order of ID/primary key). We=20
> turned on the SQL generation for OJB and verified that in the=20
> former case, the SQL select statement includes an order by=20
> clause, and in the latter case, it does not.
>=20
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the=20
> administrators:
>    http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
>    http://www.atlassian.com/software/jira
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>=20
>=20

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