[
https://issues.apache.org/jira/browse/OPENJPA-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-765:
---------------------------------
Fix Version/s: (was: 1.2.0)
> Check for insertable or updateable before checking value for null
> -----------------------------------------------------------------
>
> Key: OPENJPA-765
> URL: https://issues.apache.org/jira/browse/OPENJPA-765
> Project: OpenJPA
> Issue Type: Sub-task
> Affects Versions: 1.2.0, 1.2.1, 1.3.0, 2.0.0
> Reporter: Michael Dick
> Assignee: Michael Dick
> Fix For: 1.2.1, 1.3.0, 2.0.0
>
>
> The fix for OPENJPA-665 exposed another issue with checking for null. If the
> entity contains a "read-only" attribute (insertable=false, updatable=false)
> should we also check whether the value is null?
> A practical use case for this is a Date attribute which is automatically
> generated by the database, ie
> @Column(insertable=false, updatable=false, nullable=false,
> columnDefinition="LAST_UPD DEFAULT CURRENT_DATE")
> private Date lastUpdated;
> Before the fix for OPENJPA-665 such an attribute would not be checked for
> null.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
