Bug 95 : Oracle specific bug - treat empty strings as null... for optimistic concurrency checking without version column
Priority 
High
Reported Version 
 
Logged By 
Rob
Status 
Fixed
Fixed Version 
1.1.0
Assigned To 
 
Product 
Ebean - core
Duplicate Of 
 
Created 
25/03/2009
Updated 
25/03/2009
Type 
Bug
 
Attachments 
No attachments

See http://www.avaje.org/topic-132.html

Oracle DB treats empty strings as null. This meant there was a bug in Ebean for certain circumstances...
- optimistic concurrency checking on Update / Delete
- no version column
- likely performing insert then update or update update on the same bean... and one of the properties was set to an empty string.

This results in an Optimistic concurrency error as the empty strings needed to be treated as null.

 
Rob 25 Mar 12:10
Fixed in HEAD

Fixed in HEAD.

woResponse

Upload a file