Return-Path: 
 <ojb-dev-return-12854-apmail-db-ojb-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-ojb-dev-archive@www.apache.org
Received: (qmail 14741 invoked from network); 19 Oct 2005 05:07:35 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 19 Oct 2005 05:07:35 -0000
Received: (qmail 51944 invoked by uid 500); 19 Oct 2005 05:07:34 -0000
Delivered-To: apmail-db-ojb-dev-archive@db.apache.org
Received: (qmail 51918 invoked by uid 500); 19 Oct 2005 05:07:34 -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 25861 invoked by uid 99); 19 Oct 2005 00:37:06 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Message-ID: <969064013.1129682204978.JavaMail.jira@ajax.apache.org>
Date: Wed, 19 Oct 2005 02:36:44 +0200 (CEST)
From: "Al Lofus (JIRA)" <jira@apache.org>
To: ojb-dev@db.apache.org
Subject: [jira] Created: (OJB-75) orderby attribute in repository_user.xml not
 always respected
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

orderby attribute in repository_user.xml not always respected
-------------------------------------------------------------

         Key: OJB-75
         URL: http://issues.apache.org/jira/browse/OJB-75
     Project: OJB
        Type: Bug
  Components: PB-API  
    Versions: 1.0.3    
 Environment: All
    Reporter: Al Lofus


We have an object mapping defined that contains a collection-descriptor. That collection-descriptor uses an orderby attribute and an indirection table, as follows:

<class-descriptor class="com.dchoc.common.entity.LeagueEntity" table="LEAGUES">
    <field-descriptor id="1" name="id" column="ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true"/>
    <field-descriptor id="2" name="name" column="NAME" jdbc-type="VARCHAR"/>
    <collection-descriptor
     name="members"
     auto-retrieve="true"
     auto-update="object"
     auto-delete="object"
     proxy="true"
     indirection-table="LEAGUE_MEMBERS"
     orderby="leagueSequence"
     element-class-ref="com.dchoc.common.entity.LeagueAccountEntity">
	<fk-pointing-to-this-class column="LEAGUE_ID"/>
     	<fk-pointing-to-element-class column="LEAGUE_ACCOUNT_ID"/>
    </collection-descriptor>
</class-descriptor>

We were having problems where sometimes the objects returned in the members collection were ordered by the leagueSequence, and sometimes they weren't. From our testing, we determined that the objects in the members collection were ordered by leagueSequence when the LeagueEntity objects were obtained via a call to PersistenceBroker.getObjectByQuery(Query). When the LeagueEntity objects were obtained via a call to PersistenceBroker.getCollectionByQuery(Query), the objects in the members collection were *not* ordered by leagueSequence (they were ordered by a default order of ID/primary key). We turned on the SQL generation for OJB and verified that in the former case, the SQL select statement includes an order by clause, and in the latter case, it does not.

-- 
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: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org