Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Message-ID: <31400050.1172711572216.JavaMail.jira@brutus>
Date: Wed, 28 Feb 2007 17:12:52 -0800 (PST)
From: "Patrick Linskey (JIRA)" <jira@apache.org>
To: open-jpa-dev@incubator.apache.org
Subject: [jira] Updated: (OPENJPA-18) bulk update to Entity with secondary
 table mapping produces BAD SQL
In-Reply-To: <13880856.1155769753829.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-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Linskey updated OPENJPA-18:
-----------------------------------

    Fix Version/s: 0.9.7

> bulk update to Entity with secondary table mapping produces BAD SQL
> -------------------------------------------------------------------
>
>                 Key: OPENJPA-18
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-18
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: query
>            Reporter: David Wisneski
>             Fix For: 0.9.7
>
>
> EJBQL:   	update TwoTable t set  t.k1 = t.j2+1, t.j2= t.k1+1
> TwoTable is mapped to primary and secondary table,  tj1, tj2 are fields in primary table,  tk1, tk2 are fields in secondary table.  
> Generated SQL from the trace shows: 
> DB2 SQL error: SQLCODE: -206, SQLSTATE: 42703, SQLERRMC: J2 {prepstmnt 238685754 UPDATE ttk SET k1 = (j2 + ?), j2 = (k1 + ?) WHERE id IN (SELECT DISTINCT t0.id FROM ttk t0  INNER JOIN ttj t1 ON t0.id = t1.TwoTable_id) [params=(long) 1, (long) 1]} [code=-206, state=42703]
> Note that  column j2 is not a column of take ttk which is the secondary table.  

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