Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <16482371.15731271696269105.JavaMail.jira@thor>
Date: Mon, 19 Apr 2010 12:57:49 -0400 (EDT)
From: "Donald Woods (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Updated: (OPENJPA-1627) ORderBy with @ElementJoinColumn and
 EmbeddedId uses wrong columns in SQL
In-Reply-To: <11789427.20081271067701256.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/OPENJPA-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Donald Woods updated OPENJPA-1627:
----------------------------------

    Fix Version/s: 2.1.0
       Patch Info: [Patch Available]

the fix has been checked into trunk (2.1)
will decide later if we want this in 2.0.1

> ORderBy with @ElementJoinColumn and EmbeddedId uses wrong columns in SQL
> ------------------------------------------------------------------------
>
>                 Key: OPENJPA-1627
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1627
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.0.0-beta3
>         Environment: Windows 7 32 bit / Oracle XE
>            Reporter: Michael McGovern
>            Assignee: Fay Wang
>             Fix For: 2.1.0
>
>         Attachments: OPENJPA-1627.patch
>
>
> Typical bank example, Account with Transactions. It is a legacy db so Transaction has compound key - represented by TransactionId class.
> The problem is that the order by in the generated SQL is for columns mapped in the transaction entity NOT the TransacionId as expected.
> So the Account class has the following fragment....
> 	@OneToMany(fetch = FetchType.LAZY, cascade = {CascadeType.PERSIST})
> 	@ElementJoinColumn(name="maccno", referencedColumnName="maccno")
> 	@OrderBy(value = "_id._processDate ASC, _id._tranSequenceNumber ASC")
> 	private LinkedList<Transaction> _transactions;
> _processDate and _tranSequenceNumber are defined in the TransactionId class.
> Transaction has the following fragment....
> 	@EmbeddedId
> 	private TransactionId _id;
> 	
> 	@Column(name = "mtrancde")
> 	private int _transactionCode;
> 	
> 	@Column(name = "mamount")
> 	private BigDecimal _amount;
> 	
> 	@Column(name = "mdesc")
> 	private String _description;
> 	
> 	@Column(name = "mactdate")
> 	private Date _actualDate;
> 	
> 	@Column(name = "mbranch")
> 	private int _branch;
> And TransactionId defines the primary key columns....
> @Embeddable
> public class TransactionId {
> 	
> 	@Column(name = "maccno")
> 	private String _accountNumber;
> 	
> 	@Column(name = "mprocdate")
> 	private Date _processDate;
> 	
> 	@Column(name = "mtranseqno")
> 	private int _tranSequenceNumber;
> However the generated SQL is doing order by on columns mapped in Transaction:
> executing prepstmnt 23188098 SELECT t0.maccno, t0.mprocdate, t0.mtranseqno, t0.mactdate, t0.mamount, t0.mbranch, t0.mchqcash, t0.mdesc,
>  t0.mtmnlno, t0.mtrancde, t0.mtrnfeed 
> FROM transaction t0 
> WHERE t0.maccno = ? 
> ORDER BY t0.mamount ASC, t0.mbranch ASC [params=(String) 000734123]
> (no idea why it chose mamount, mbranch)
> The last line should be:
> ORDER BY t0.mprocdate ASC, t0.mtranseqno ASC [params=(String) 000734123]
> Thanks
> Michael

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.