Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.1, 1.3.0, 2.0.0-M1
    • Fix Version/s: 1.2.1, 1.3.0, 2.0.0-M1, 2.0.0-M2
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Michael Dick
            Reporter:
            Michael Dick
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development