This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I know this isn't the place but didn't find anything related to Java Persistence. The classes generated from the database don't take into account the unique key. Hibernate does support this. See: http://docs.jboss.org/ejb3/app-server/HibernateAnnotations/reference/en/html_single/index.html Section 2.2.1.1. Defining the table
I believe the correct category for this would be J2EE > Persistence. Reassigning to them...
*** This issue has been marked as a duplicate of 76357 ***
Whoops, not a duplicate.
The unique constraints are used for schema generation, that's why the wizard doesn't generate them. Since you already have the tables, it seems unlikely to want to generate them again from the entity classes.
http://hg.netbeans.org/main/rev/7379c3d2af36
In NetBean 6.5, there is an additional step (last step and optional) to allow the user to specify if Attributes for Regenerating Tables should be generated. Unique constraints will be generated on @Table if the option is checked. http://hg.netbeans.org/main?cmd=changeset;node=ec8e1f01702d