Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <1717134550.1210018555576.JavaMail.jira@brutus>
Date: Mon, 5 May 2008 13:15:55 -0700 (PDT)
From: "Michael Dick (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Assigned: (OPENJPA-590) The push-down sql for JPQL has
 unpredictable ordering in the set clause for update statement
In-Reply-To: <1704148758.1209883075679.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Michael Dick reassigned OPENJPA-590:
------------------------------------

    Assignee: Michael Dick

> The push-down sql for JPQL has unpredictable ordering in the set clause for update statement
> --------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-590
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-590
>             Project: OpenJPA
>          Issue Type: Bug
>            Reporter: Fay Wang
>            Assignee: Michael Dick
>         Attachments: openjpa.patch
>
>
>       Our application requires the push-down sql from named/dynamic query be the same each time a same JPQL is executed. 
> In the following JPQL example, however, 
> 	
>       query="UPDATE BasicA t set t.name= ?1, t.age = ?2 WHERE t.id = ?3"
>       we observe that two different push-down sql could be generated:
>       
>       UPDATE PDQBasicA t0 SET name = ?, age = ? WHERE (t0.id = ?)
>       UPDATE PDQBasicA t0 SET age = ?, name = ? WHERE (t0.id = ?)
>       This unpredictable behavior breaks our application. The indeterministic ordering of the update list is due to the indeterministic ordering provided by HashMap and HashSet in QueryExpressions and JPQLExpressionBuilder, respectively.
>       When the HashMap is changed to LinkedHashMap and HashSet to LinkedHashSet, the access order based on insertion will be preserved and the generated push-down sql will have predictable ordering of update list. The attached patch fixes this problem.

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