[
https://issues.apache.org/jira/browse/OPENJPA-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460519#comment-13460519
]
garpinc edited comment on OPENJPA-2263 at 9/22/12 1:32 AM:
-----------------------------------------------------------
This contains the test case that illustrates that a dirty field will cause the
pk to be updated although it hasn't changed.. Once again this is likely
expected behavior but it did give me a bump in the road.. Test case in this is:
TestCollectionValueMapper.testUpdatePk()
was (Author: garpinc):
test case to try is the testSelect0 one. When run in the console you will
see the select in the trace right after the last alter table
> 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
>
> Attachments: testselect0.zip
>
>
> 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
