[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-140?page=co... ] Erwin Bolwidt commented on ANN-140: ----------------------------------- I don't understand Gavin's stance on this issue. Yes, Hibernate is very smart and its way of doing joined subclasses has superios performance over implementations that require a discriminator column. But hibernate's algorithm doesn't prevent a discriminator column. In fact, Hibernate itself supports discriminator columns with joined subclasses, so why are you explicitly disallowing it in hibernate annotations? It leaves users out in the cold who are using a legacy database; the only way to get around it is to not use annotations for the superclass and all subclasses. In addition to that, even if a discriminator column never gives any performance bonuses, it still makes the database model more resilient. If for some reason (dbas mucking about the database by hand, other apps interfering with the direct use of sql) data ends up in multiple subclass tables, a discriminator column makes it possible to clean up the database, since it is the judge on what the intended subclass was. Please change the three lines of code and make it possible to configure discriminator columns with joined subclasses using hibernate annotations. -- 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