Rejected
Details
Assignee
UnassignedUnassignedReporter
Marc SchipperheynMarc SchipperheynComponents
Affects versions
Priority
Minor
Details
Details
Assignee
Unassigned
UnassignedReporter
Marc Schipperheyn
Marc SchipperheynComponents
Affects versions
Priority
Created May 3, 2011 at 1:44 PM
Updated April 22, 2015 at 6:24 PM
Resolved May 5, 2011 at 2:19 PM
This bug has already been referred to in but was incorrectly marked as solved.
The core issue is that when the columnNames attribute is used to specify multiple columns in the index, and we use Hibernate to generate the database, only one column is actually turned on in the index.
According to the Hibernate team this is because if you want to use the columnNames attribute, you have to use the annotation at the class level. However, this is considered illegal use and therefore not possible.
Either class level use should be made legal for the annotation or the parser should actually parse the columnNames attribute at the classlevel. The latter seems more logical. In the end, it is a major inconvenience not to mention error prone to manually have to specify all the combined Index Fields.