Revised default behaviour for back reference naming.
The new default is to take `@Table` annotations into account. The behaviour can be configured by setting the `foreignKeyNaming` property on the `RelationalMappingContext`. Closes #1162 See #1147 Original pull request: #1324.
This commit is contained in:
committed by
Mark Paluch
parent
40446f9ca9
commit
d7f2a27ee9
@@ -134,7 +134,7 @@ public class SqlGeneratorFixedNamingStrategyUnitTests {
|
||||
|
||||
assertThat(sql)
|
||||
.isEqualTo("DELETE FROM \"FIXEDCUSTOMSCHEMA\".\"FIXEDCUSTOMTABLEPREFIX_SECONDLEVELREFERENCEDENTITY\" "
|
||||
+ "WHERE \"FIXEDCUSTOMSCHEMA\".\"FIXEDCUSTOMTABLEPREFIX_SECONDLEVELREFERENCEDENTITY\".\"REFERENCED_ENTITY\" IN "
|
||||
+ "WHERE \"FIXEDCUSTOMSCHEMA\".\"FIXEDCUSTOMTABLEPREFIX_SECONDLEVELREFERENCEDENTITY\".\"FIXEDCUSTOMTABLEPREFIX_REFERENCEDENTITY\" IN "
|
||||
+ "(SELECT \"FIXEDCUSTOMSCHEMA\".\"FIXEDCUSTOMTABLEPREFIX_REFERENCEDENTITY\".\"FIXEDCUSTOMPROPERTYPREFIX_L1ID\" "
|
||||
+ "FROM \"FIXEDCUSTOMSCHEMA\".\"FIXEDCUSTOMTABLEPREFIX_REFERENCEDENTITY\" "
|
||||
+ "WHERE \"FIXEDCUSTOMSCHEMA\".\"FIXEDCUSTOMTABLEPREFIX_REFERENCEDENTITY\".\"DUMMY_ENTITY\" = :rootId)");
|
||||
@@ -170,7 +170,7 @@ public class SqlGeneratorFixedNamingStrategyUnitTests {
|
||||
|
||||
assertThat(sql)
|
||||
.isEqualTo("DELETE FROM \"FIXEDCUSTOMSCHEMA\".\"FIXEDCUSTOMTABLEPREFIX_SECONDLEVELREFERENCEDENTITY\" "
|
||||
+ "WHERE \"FIXEDCUSTOMSCHEMA\".\"FIXEDCUSTOMTABLEPREFIX_SECONDLEVELREFERENCEDENTITY\".\"REFERENCED_ENTITY\" IN "
|
||||
+ "WHERE \"FIXEDCUSTOMSCHEMA\".\"FIXEDCUSTOMTABLEPREFIX_SECONDLEVELREFERENCEDENTITY\".\"FIXEDCUSTOMTABLEPREFIX_REFERENCEDENTITY\" IN "
|
||||
+ "(SELECT \"FIXEDCUSTOMSCHEMA\".\"FIXEDCUSTOMTABLEPREFIX_REFERENCEDENTITY\".\"FIXEDCUSTOMPROPERTYPREFIX_L1ID\" "
|
||||
+ "FROM \"FIXEDCUSTOMSCHEMA\".\"FIXEDCUSTOMTABLEPREFIX_REFERENCEDENTITY\" "
|
||||
+ "WHERE \"FIXEDCUSTOMSCHEMA\".\"FIXEDCUSTOMTABLEPREFIX_REFERENCEDENTITY\".\"DUMMY_ENTITY\" IS NOT NULL)");
|
||||
|
||||
@@ -67,7 +67,7 @@ public class PartTreeJdbcQueryUnitTests {
|
||||
|
||||
private static final String TABLE = "\"users\"";
|
||||
private static final String ALL_FIELDS = "\"users\".\"ID\" AS \"ID\", \"users\".\"AGE\" AS \"AGE\", \"users\".\"ACTIVE\" AS \"ACTIVE\", \"users\".\"LAST_NAME\" AS \"LAST_NAME\", \"users\".\"FIRST_NAME\" AS \"FIRST_NAME\", \"users\".\"DATE_OF_BIRTH\" AS \"DATE_OF_BIRTH\", \"users\".\"HOBBY_REFERENCE\" AS \"HOBBY_REFERENCE\", \"hated\".\"NAME\" AS \"HATED_NAME\", \"users\".\"USER_CITY\" AS \"USER_CITY\", \"users\".\"USER_STREET\" AS \"USER_STREET\"";
|
||||
private static final String JOIN_CLAUSE = "FROM \"users\" LEFT OUTER JOIN \"HOBBY\" \"hated\" ON \"hated\".\"USER\" = \"users\".\"ID\"";
|
||||
private static final String JOIN_CLAUSE = "FROM \"users\" LEFT OUTER JOIN \"HOBBY\" \"hated\" ON \"hated\".\"USERS\" = \"users\".\"ID\"";
|
||||
private static final String BASE_SELECT = "SELECT " + ALL_FIELDS + " " + JOIN_CLAUSE;
|
||||
|
||||
JdbcMappingContext mappingContext = new JdbcMappingContext();
|
||||
|
||||
@@ -32,7 +32,7 @@ public class DefaultNamingStrategy implements NamingStrategy {
|
||||
*/
|
||||
public static NamingStrategy INSTANCE = new DefaultNamingStrategy();
|
||||
|
||||
private ForeignKeyNaming foreignKeyNaming = ForeignKeyNaming.IGNORE_RENAMING;
|
||||
private ForeignKeyNaming foreignKeyNaming = ForeignKeyNaming.APPLY_RENAMING;
|
||||
|
||||
@Override
|
||||
public void setForeignKeyNaming(ForeignKeyNaming foreignKeyNaming) {
|
||||
|
||||
@@ -36,7 +36,7 @@ public class RelationalMappingContext
|
||||
|
||||
private final NamingStrategy namingStrategy;
|
||||
private boolean forceQuote = true;
|
||||
private ForeignKeyNaming foreignKeyNaming = ForeignKeyNaming.IGNORE_RENAMING;
|
||||
private ForeignKeyNaming foreignKeyNaming = ForeignKeyNaming.APPLY_RENAMING;
|
||||
|
||||
/**
|
||||
* Creates a new {@link RelationalMappingContext}.
|
||||
|
||||
@@ -249,10 +249,10 @@ Also, the type of that aggregate is encoded in a type parameter.
|
||||
==== Back References
|
||||
|
||||
All references in an aggregate result in a foreign key relationship in the opposite direction in the database.
|
||||
By default, the name of the foreign key column is the table name of the referencing entity, ignoring any table annotations.
|
||||
By default, the name of the foreign key column is the table name of the referencing entity.
|
||||
|
||||
Alternatively you may choose to have them named by the actual table name of the referencing entity.
|
||||
You activate this behaviour by calling `setForeignKeyNaming(ForeignKeyNaming.APPLY_RENAMING)` on the `RelationalMappingContext`.
|
||||
Alternatively you may choose to have them named by the entity name of the referencing entity ignoreing `@Table` annotations.
|
||||
You activate this behaviour by calling `setForeignKeyNaming(ForeignKeyNaming.IGNORE_RENAMING)` on the `RelationalMappingContext`.
|
||||
|
||||
For `List` and `Map` references an additional column is required for holding the list index or map key. It is based on the foreign key column with an additional `_KEY` suffix.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user