|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
06/Jul/07 02:50 PM
|
|
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.
|
|
Description
|
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. |
Show » |
made changes - 06/Jul/07 02:50 PM
| Field |
Original Value |
New Value |
|
Resolution
|
|
Fixed
[ 1
]
|
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
|
Improvement
Resolved
Major
Bulk updates: version information should be automatically maintained when the query does not
