You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the current version of Hibernate (4.2.2.Final) and JPA (Hibernate JPA 1.0.1.Final), the following issues arise:
current on Connector is a reserved keyword. Fixable by adding an @Column annotation with a different name
Table and column names should not exceed 30 characters. At the time of writing, this applies to the operator-api module:
io.motown.operatorapi.viewmodel.persistence.entities.ChargingStation.localAuthorizations will be generated into table ChargingStation_localAuthorizations
io.motown.operatorapi.viewmodel.persistence.entities.ChargingStation.configurationItems will be generated into table ChargingStation_configurationItems
Oracle does not support @GeneratedValue(strategy = GenerationType.IDENTITY) until Oracle 12c. For Oracle10g Dialect, use a @SequenceGenerator
example
@Id
@SequenceGenerator(name="seq", allocationSize=1, initialValue=1)
@GeneratedValue(generator="seq")
private Long id;
note
These issues arose with Oracle10g Dialect, configurable in the jpaVendorAdapter as such:
When using the current version of Hibernate (4.2.2.Final) and JPA (Hibernate JPA 1.0.1.Final), the following issues arise:
current
onConnector
is a reserved keyword. Fixable by adding an@Column
annotation with a different nameTable and column names should not exceed 30 characters. At the time of writing, this applies to the operator-api module:
io.motown.operatorapi.viewmodel.persistence.entities.ChargingStation.localAuthorizations
will be generated into tableChargingStation_localAuthorizations
io.motown.operatorapi.viewmodel.persistence.entities.ChargingStation.configurationItems
will be generated into tableChargingStation_configurationItems
Oracle does not support
@GeneratedValue(strategy = GenerationType.IDENTITY)
until Oracle 12c. For Oracle10g Dialect, use a@SequenceGenerator
example
note
These issues arose with Oracle10g Dialect, configurable in the jpaVendorAdapter as such:
The text was updated successfully, but these errors were encountered: