SQL : Naming clash between column and primary key
Bug #674917 reported by
Timo Westkämper
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Querydsl |
Fix Released
|
High
|
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(
public final PrimaryKey<
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 |
To post a comment you must log in.
This can now be avoided by using the innerClassesFor Keys=true option in the Maven plugin or Ant task or creating the serializer like this :
Serializer serializer = new MetaDataSeriali zer(namePrefix, namingStrategy, true);