|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Where are you seeing usage of this NamingStrategy? Do you specify it explicitly?
TBH, the whole notion of NamingStrategy is broke in my opinion. And unfortunately fixing it requires major changes, and since this is a contract we know is quite often implemented by user code that means waiting for a major version. Currently that is scheduled under 5.0, part of which is basically splitting NamingStrategy up into 2 different contracts. See HHH-7078 for further details on that.