[jira] [Resolved] (OPENJPA-2263) Update statements should not update the primary key of database unless the primary key has in fact changed

["garpinc (JIRA)" <ji...@apache.org>]

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

garpinc resolved OPENJPA-2263.
------------------------------

       Resolution: Not A Problem
    Fix Version/s: 2.2.0

In creating the test case I found out that OpenJPAPersistence.cast(em).dirty(wrapper, fieldName) was called on the primary key field.

I guess it's speculative whether a call like should trigger behavior like this if the field hasn't in fact changed so i've decided it's not a problem and i just did not make the primary key as dirty.
                
> Update statements should not update the primary key of database unless the primary key has in fact changed
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-2263
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2263
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 2.2.0
>            Reporter: garpinc
>             Fix For: 2.2.0
>
>
> I have encountered a situation while creating an openjpa dictionary for teradata. It seems teradata does not like it when the primary key is updated. 
> i.e: update tablex set pk=1 where pk=1;
> Following the code it seems RowImpl.java contains a method getUpdateSQL which uses the dictionary to various things but it doesn't allow the dictionary to change the statement itself. 
> The specific functionality I need here is to only update the pk if the pk has changed or maybe an option not to update the pk at all.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira