Home » Bugs » BUG 330 : DDL Generating check constraint with name including "null"
 Bug 330 : DDL Generating check constraint with name including "null"
Priority 
High
 Reported Version 
 
 Logged By 
Rob
Status 
Fixed
 Fixed Version 
2.7.0
 Assigned To 
 
Product 
Ebean - core
 Duplicate Of 
 
 Created 
13/10/2010
Updated 
13/10/2010
 Type 
Bug
  
Attachments 
No attachments

Hi, I think there is a small bug in Ebean generated DDL SQL.

when I define an enumerated type in a class Ebean puts a constraint in
the DDL statement for the relative table:
constraint ck_null_tipo check (tipo in ('dec','str','data','int')).
I have the same enumerated type in more than one class, but the
generated constraint name remains the same and the DB complains.

Yours sincerely

Claudio
 
Rob 13 Oct 09:39
Ok

I believe the Enum property was on an embedded bean.

Fixed to always use the current table name being created rather than determine the table name from the current BeanDescriptor.

Fixed in HEAD.

woResponse

Upload a file