About unique

release

2.5.1

... ( issue #78 ). Added support of @Column(unique="true") and equivalent ORM XML ( issue #79 ). Fixed ...

 
release

2.5.2

... ( issue #78 ). Added support of @Column(unique="true") and equivalent ORM XML ( issue #79 ). Fixed ...

 
release

2.5.3

... ( issue #78 ). Added support of @Column(unique="true") and equivalent ORM XML ( issue #79 ). Fixed ...

 
release

2.5.4

... ( issue #78 ). Added support of @Column(unique="true") and equivalent ORM XML ( issue #79 ). Fixed ...

 
release

2.5.0

... ( issue #78 ). Added support of @Column(unique="true") and equivalent ORM XML ( issue #79 ). Fixed ...

 
release

2.4.7

... ( issue #78 ). Added support of @Column(unique="true") and equivalent ORM XML ( issue #79 ). Fixed ...

 
forum_thread

Duplicate Entity class names causes Exception in Query

I have two Entities which have the same class name but reside in different packages, only one of them is mentioned in the persistence.xml. I a NamedQuery I use the unqualified class name of one of these entities. If I execute that query I get an exception;   ... test apps! Thanks for your help. BTW the @Unique annotations for non @id attributes makes our JP QL fly! ...

 
release

2.4.5

... ( issue #78 ). Added support of @Column(unique="true") and equivalent ORM XML ( issue #79 ). Fixed ...

 
release

2.4.6

... ( issue #78 ). Added support of @Column(unique="true") and equivalent ORM XML ( issue #79 ). Fixed ...

 
forum_thread

em.flush(); em.clear(); loosing data and not persisting managed objects

I'm having trouble with flush() and clear() in a loop inside a transaction not persisting modified objects to database. Sometimes it does other times it doesn't. Here is my Entity. ... object that is always a 40 digit hex string and should be unique among the key fields.   For one of those three ...