Skip to:

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

Hibernate core test cases use Teradata reserved words

Description

This occurs in many of the Core tests and I've generally been able to fix the problem via backticks, @Column notation etc.

There are 6 test cases however, where I've been unable to get rid of the Teradata reserved words. These are:

1)Reserved word - summary

org.hibernate.test.annotations.collectionelement.OrderByTest
testOrderByWithDottedNotation

2) Reserved word - type

org.hibernate.test.annotations.referencedcolumnname.ReferencedColumnNameTest
testUnidirectionalOneToMany

3) Reserved word - title

org.hibernate.test.annotations.indexcoll.IndexedCollectionTest
testMapKeyOnManyToMany
testMapKeyOnManyToManyOnId

4) Reserved word - year
org.hibernate.test.annotations.xml.ejb3
testEjb3Xml

5) Reserved word - title

org.hibernate.test.subclassfilter.UnionSubClassFilterTest
testFiltersWithUnionSubclass

6) Reserved word - title

org.hibernate.test.unionsubclass2.UnionSubClassTest
testCustomColumnReadAndWrite
testQuerySubclassAttribute
testUnionSubclass

Activity

Show:

Christian Beikov June 24, 2021 at 9:33 AM

I changed a few tests to avoid the use of reserved words, but I have no way of testing this. The Teradata dialect is moved to the hibernate-community-dialects artifact as part of https://hibernate.atlassian.net/browse/HHH-14693#icft=HHH-14693

Steve Ebersole October 28, 2015 at 3:24 AM

As part of verifying that this issue affects 5.0, please just set the "Affects version". Leave the "verify-affects-5.0" label and leave the issue in "Awaiting Response" status; these are critical for us to be able to track these verifications and triage them. Thanks.

Steve Ebersole October 27, 2015 at 7:16 PM

This bug report does not indicate that the reported issue affects version 5.x. Versions prior to 5.x are no longer maintained. It would be a great help to the Hibernate team and community for someone to verify that the reported issue still affects version 5.x. If so, please add the 5.x version that you verified with to the list of affected-versions and attach the (preferably SSCCE) test case you used to do the verification to the report; from there the issues will be looked at during our triage meetings.

For details, see http://in.relation.to/2015/10/27/great-jira-cleanup-2015/

Out of Date

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

Created April 18, 2013 at 9:13 PM
Updated June 24, 2021 at 9:33 AM
Resolved June 24, 2021 at 9:33 AM

Flag notifications