[hibernate-issues] [Hibernate-JIRA] Commented: (ANN-140) Discriminator column not supported with JOINED strategy

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-140?page=co... ] Amit Kasher commented on ANN-140: --------------------------------- I'd like to add another possible requirement for discriminator column support. If you have a discriminator column, you can have it inside DB constraints, and achieve constraints in which subclasses participate as different entities. Example: I have the following entities: A { id, name } B extends A { height } C extends A { width } I need the following constraint: I don't want to allow (more than 1:) 2 or more instances of B with the same name, and I don't want (more than 1:) 2 or more instances of C with the same name. However, I DO want to allow 1 instance of B with the name "Jack", and another instance, this time of C, with that same name, "Jack". The only way to achieve this, I think, is having a discriminator column in A which will allow you to define a unique constraint containing A.discriminator and A.name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira