Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <7608616.1183321864477.JavaMail.jira@brutus>
Date: Sun, 1 Jul 2007 13:31:04 -0700 (PDT)
From: "Patrick Linskey (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Created: (OPENJPA-275) Bulk updates: version information
 should be automatically maintained when the query does not
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Bulk updates: version information should be automatically maintained when the query does not
--------------------------------------------------------------------------------------------

                 Key: OPENJPA-275
                 URL: https://issues.apache.org/jira/browse/OPENJPA-275
             Project: OpenJPA
          Issue Type: Improvement
          Components: jdbc, query
    Affects Versions: 0.9.7, 0.9.6, 0.9.0
            Reporter: Patrick Linskey
            Assignee: Patrick Linskey
             Fix For: 1.0.0


According to the JPA specification, the user must manually maintain the @Version column in objects that are updated via a bulk update. This is a potential bug in the waiting, and is impossible to do correctly for time-based version fields.

OpenJPA should automatically increment version counters when a bulk update is issued that does not maintain version counters itself.

Of course, this will not change the fact that bulk updates do not do any optimistic lock checks; that behavior is inherent to the nature of bulk updates in the JPA specification, since they are evaluated entirely against the database.

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