Unique constraint not created in JPA

Question

I have created the following entity bean, and specified two columns as being unique. Now my problem is that the table is created without the unique constraint, and no errors

Answer 1

Well, I found another way to make the design. More because the design evolved than a work around.
I heard however from a colleague, that had had the same problem, that unique constraint only are created by hibernate (we are running JBoss 4.3) when the entire database is created. It will not work when you create a new table in an existing database.
So in persistence.xml it is necessary to set hibernate.hbm2ddl.auto to create-drop to make it work. I can not confirm this though.

Answer 2

You dont have to drop everything, just drop this particular table you want to create unique index for

Answer 3

I also faced the same issue, but adding unique-key="UK1_test" in the mapping file worked fine.

<property name="hibernate.hbm2ddl.auto">create</property> with unique-key="UK1_test" unique="true" in the mapping file created alter table employee add constraint UK1_test unique (addrId)

Answer 4

If you want the unique constraint, you should do it by sql:

ALTER TABLE cm_blockList ADD CONSTRAINT cm_blockList_unq UNIQUE (terminal);

See also: https://stackoverflow.com/a/3498242/1244488

Answer 5

More suggestions than a real answer...

• you should clarify which JPA provider (and the version) you are using for such questions.

• I notice that one of your column is part of a ManyToOne association, this might be a "special" case not well handled by your JPA provider. By not well handled, I mean bug. I'd check the issue tracker for an existing issue (and maybe create a new one, your case seems JPA compliant).