SQL : Naming clash between column and primary key

Bug #674917 reported by Timo Westkämper on 2010-11-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Timo Westkämper

Bug Description

When column and primary key share the same name invalid Java classes are generated :

  public final NumberPath<Long> expertRuleID = createNumber("ExpertRuleID", Long.class);

  public final PrimaryKey<QExpertRule> expertRuleID = createPrimaryKey(expertRuleID);

Changed in querydsl:
assignee: nobody → Timo Westkämper (timo-westkamper)
importance: Undecided → High
status: New → In Progress
Changed in querydsl:
status: In Progress → Fix Committed

This can now be avoided by using the innerClassesForKeys=true option in the Maven plugin or Ant task or creating the serializer like this :

Serializer serializer = new MetaDataSerializer(namePrefix, namingStrategy, true);

Changed in querydsl:
status: Fix Committed → Fix Released

Released in 2.0.5

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers