Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Quoting identifiers breaks @UniqueConstraint

Description

When hibernate.globally_quoted_identifiers is set to true, defining custom @UniqueConstraint is not possible. Error message is: "org.hibernate.AnnotationException: Unable to create unique key constraint (<columns>) on table <table>: database column <column> not found. Make sure that you use the correct column name which depends on the naming strategy in use (it may not be the same as the property name in the entity, especially for relational types)".

Attachments

1

Activity

Show:

Jay XuOctober 14, 2013 at 9:48 AM

Seems this bug regresses in 4.2.6. Our project starts with the same exception after upgrading from 4.2.5 to 4.2.6, with code / configuration unchange

Brett MeyerMarch 7, 2013 at 7:06 PM

, spot on analysis. Thanks

Sergey ParhomenkoDecember 24, 2012 at 3:03 PM

From what I see in the code, Configuration.MappingsImpl.TableColumnNameBinding.logicalToPhysical map is using unquoted logical column name as key (unless naming strategy is explicitly quoting logical column names, which is not the cases with default naming strategy, and probably should never be the case). Whereas Configuration.buildUniqueKeyFromColumnNames() method, which is using this map to transform user-provided logical column names to physical names, always quotes the logical name before doing the lookup, thus causing the issue.

Sergey ParhomenkoDecember 24, 2012 at 2:40 PM
Edited

If that helps, the relevant part of error stacktrace is:

Sergey ParhomenkoDecember 24, 2012 at 2:38 PM

Attached a unit test which demonstrates the issue and the workaround described above.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created December 24, 2012 at 2:33 PM
Updated October 14, 2013 at 9:48 AM
Resolved March 7, 2013 at 7:07 PM