Reputation: 3053
Hibernate has some standard naming strategies implemented:
default
for org.hibernate.boot.model.naming.ImplicitNamingStrategyJpaCompliantImpl - an alias for jpa
jpa
for org.hibernate.boot.model.naming.ImplicitNamingStrategyJpaCompliantImpl - the JPA 2.0 compliant naming strategy
legacy-hbm
for org.hibernate.boot.model.naming.ImplicitNamingStrategyLegacyHbmImpl - compliant with the original Hibernate NamingStrategy
legacy-jpa
for org.hibernate.boot.model.naming.ImplicitNamingStrategyLegacyJpaImpl - compliant with the legacy NamingStrategy developed for JPA 1.0, which was unfortunately unclear in many respects regarding implicit naming rules.
component-path
for org.hibernate.boot.model.naming.ImplicitNamingStrategyComponentPathImpl - mostly follows ImplicitNamingStrategyJpaCompliantImpl rules, except that it uses the full composite paths, as opposed to just the ending property part
But I can't find any examples for each strategy. Do you have any idea where I can find such examples?
Upvotes: 24
Views: 11519
Reputation: 2686
Here is an example, which shows differences between these four naming strategies (used Hibernate 5.2.11.RELEASE
).
@Entity
@Table(name = "mainTable")
public class MainEntity {
@Id
private Long id;
@ElementCollection
Set<EmbeddableElement> mainElements;
@OneToMany(targetEntity = DependentEntity.class)
Set<DependentEntity> dependentEntities;
@OneToOne(targetEntity = OwnedEntity.class)
OwnedEntity ownedEntity;
}
@Entity
@Table(name = "dependentTable")
public class DependentEntity {
@Id
private Long id;
@ManyToOne
MainEntity mainEntity;
@ElementCollection
@CollectionTable(name = "dependentElements")
Set<EmbeddableElement> dependentElements;
}
@Entity(name = "`owned_table`")
public class OwnedEntity {
@Id
private Long id;
@ElementCollection
@CollectionTable
Set<EmbeddableElement> ownedElements;
}
@Embeddable
public class EmbeddableElement {
@Column(name = "`quotedField`")
String quotedField;
@Column
String regularField;
}
Default naming strategy. Implementation of the ImplicitNamingStrategy contract, generally preferring to conform to JPA standards.
create table main_table
(id bigint not null, "owned_entity_id" bigint, primary key (id))
create table main_entity_main_elements
(main_entity_id bigint not null, "quoted_field" varchar(255), regular_field varchar(255))
create table main_table_dependent_table
(main_entity_id bigint not null, dependent_entities_id bigint not null, primary key (main_entity_id, dependent_entities_id))
create table dependent_table
(id bigint not null, main_entity_id bigint, primary key (id))
create table dependent_elements
(dependent_entity_id bigint not null, "quoted_field" varchar(255), regular_field varchar(255))
create table "owned_table"
(id bigint not null, primary key (id))
create table "`owned_table`_owned_elements"
("`owned_table`_id" bigint not null, "quoted_field" varchar(255), regular_field varchar(255))
Implements the original legacy naming behavior.
The main differences with the default strategy are:
create table main_table
(id bigint not null, owned_entity bigint, primary key (id))
create table main_entity_main_elements
(main_entity_id bigint not null, "quoted_field" varchar(255), regular_field varchar(255))
create table main_table_dependent_entities
(main_entity_id bigint not null, dependent_entities bigint not null, primary key (main_entity_id, dependent_entities))
create table dependent_table
(id bigint not null, main_entity bigint, primary key (id))
create table dependent_elements
(dependent_entity_id bigint not null, "quoted_field" varchar(255), regular_field varchar(255))
create table owned_entity
(id bigint not null, primary key (id))
create table owned_entity_owned_elements
(owned_entity_id bigint not null, "quoted_field" varchar(255), regular_field varchar(255))
Implementation of the ImplicitNamingStrategy contract which conforms to the naming rules initially implemented by Hibernate for JPA 1.0, prior to many things being clarified.
The main differences with the default strategy are:
create table main_table
(id bigint not null, "owned_entity_id" bigint, primary key (id))
create table main_table_main_elements
(main_table_id bigint not null, "quoted_field" varchar(255), regular_field varchar(255))
create table main_table_dependent_table
(main_table_id bigint not null, dependent_entities_id bigint not null, primary key (main_table_id, dependent_entities_id))
create table dependent_table
(id bigint not null, main_entity_id bigint, primary key (id))
create table dependent_elements
(dependent_table_id bigint not null, "quoted_field" varchar(255), regular_field varchar(255))
create table "owned_table"
(id bigint not null, primary key (id))
create table "owned_table_owned_elements"
("owned_table_id" bigint not null, "quoted_field" varchar(255), regular_field varchar(255))
An ImplicitNamingStrategy implementation which uses full composite paths extracted from AttributePath, as opposed to just the terminal property part.
The main difference with the default strategy is:
create table main_table
(id bigint not null, "owned_entity_id" bigint, primary key (id))
create table main_entity_main_elements
(main_entity_id bigint not null, "quoted_field" varchar(255), main_elements_regular_field varchar(255))
create table main_table_dependent_table
(main_entity_id bigint not null, dependent_entities_id bigint not null, primary key (main_entity_id, dependent_entities_id))
create table dependent_table
(id bigint not null, main_entity_id bigint, primary key (id))
create table dependent_elements
(dependent_entity_id bigint not null, "quoted_field" varchar(255), dependent_elements_regular_field varchar(255))
create table "owned_table"
(id bigint not null, primary key (id))
create table "`owned_table`_owned_elements"
("`owned_table`_id" bigint not null, "quoted_field" varchar(255), owned_elements_regular_field varchar(255))
Upvotes: 17