]
Marc Schipperheyn commented on HHH-6185:
----------------------------------------
That should be: Either class level use should be made legal for the annotation or the
parser should actually parse the columnNames attribute at the method level
@Index doesn't create multi-column indexes
------------------------------------------
Key: HHH-6185
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6185
Project: Hibernate Core
Issue Type: Bug
Components: annotations
Affects Versions: 3.6.3
Reporter: Marc Schipperheyn
Priority: Minor
This bug has already been referred to in ANN-597 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: