[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1976?page=all ] Samppa Saarela updated HHH-1976: -------------------------------- Attachment: hibernate-annotations-3.2.1.patch.txt This bug was due to misusage of default entity name which is unqualified class name according to EJB3 spec to derive the table name using given NamingStrategy. This patch fixes the issue. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-565?page=co... ] Emmanuel Bernard commented on ANN-565: -------------------------------------- This all came from ANN-330 Here is the problem The spec mandate to use table name == entity name Then entity name can be explicit or implicit (unqualified classname) Then we have Hibernate Core that calls classToTableName if table is not null So there is some sort of a missmatch here. A clean solution would be : - we always call tableName(entityName) since the spec "force" a table name one way or an other => this prevent people from using the fqcn for tables A somewhat incoherent solution would be: - if entity name is implicit, then we call classToTableName(className) - if entity name is explicit, then we call tableName(entityName) //ie like if the table were explicit The current solution does - we always call classToTableName(entityName) which clearly is broken. WDYT? -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-565?page=co... ] Max Rydahl Andersen commented on ANN-565: ----------------------------------------- so EJB3 needs their own table naming strategy ? or you need to have an option on entitymanager to the FQN instead of the simple name when binding ? -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-565?page=co... ] Max Rydahl Andersen commented on ANN-565: ----------------------------------------- btw. the workaround is to explicitly specify/duplicate the entityname in the entities, correct? (annoying, but should work, right ?) -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-565?page=co... ] Max Rydahl Andersen commented on ANN-565: ----------------------------------------- package some.pack.name; @Entity(name="some.pack.name.MyClass") public class MyClass { .... } (I always forget why the above is not the default anyway) -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-565?page=co... ] Emmanuel Bernard commented on ANN-565: -------------------------------------- you already can use such keywords by backticking them `User`. But year, Oracle forbid half of the English dictionary, you'd better switch to French ;-) -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4312?page=c... ] Manuel Bernhardt commented on HHH-4312: --------------------------------------- Just got hit with this as well, it's kinda annoying (I picture myself manually naming all entities by hand to get the full class names). What about the "getDefaultEntityName(String className)"? I think it's a good approach. It would most likely break drop-in replacement for existing naming strategy implementations (they'd miss the method) but OTOH this bug renders the NamingStrategy unusable when wanting to do things like a NamespaceNamingStrategy. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4312?page=c... ] Steve Ebersole closed HHH-4312. ------------------------------- Resolution: Fixed I am thinking at this point that we can simply say this will be fixed by HHH-6077 -- 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