|
||||||||
|
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 |
||||||||
This is a nasty bug, IMO, with very bad results. It manifests itself with Grails (http://jira.grails.org/browse/GRAILS-9105) due to their default naming scheme, which uses the same base for the column names.
One thing to add, is that the uniqueInteger on the Table object depends on the order in which it is instantiated, hence making this a hard bug to reproduce.