Querydsl

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
	Querydsl	Fix Released	High	Timo Westkämper

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);

Timo Westkämper (timo-westkamper) on 2010-11-19

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

Timo Westkämper (timo-westkamper) on 2010-11-19

Changed in querydsl:
status:	In Progress → Fix Committed

Revision history for this message

Timo Westkämper (timo-westkamper) wrote on 2010-11-22:

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

Revision history for this message

Timo Westkämper (timo-westkamper) wrote on 2010-11-22:

Released in 2.0.5

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Bug watches keep track of this bug in other bug trackers.