CODEWITHSUNDEEP
javasql-serverhibernateormjpa
TJR
TJR

Reputation: 3773

How to map an entity field whose name is a reserved word in JPA

@Column(name="open")

Using sqlserver dialect with hibernate.

[SchemaUpdate] Unsuccessful: create table auth_session (id numeric(19,0) identity not null, active tinyint null, creation_date datetime not null, last_modified datetime not null, maxidle int null, maxlive int null, open tinyint null, sessionid varchar(255) not null, user_id numeric(19,0) not null, primary key (id), unique (sessionid))
[SchemaUpdate] Incorrect syntax near the keyword 'open'.

I would have expected hibernate to use quoted identifier when creating the table.

Any ideas on how to handle this... other than renaming the field?

Upvotes: 123

Views: 80033

Answers (8)

Pascal Thivent
Pascal Thivent

Reputation: 570385

With Hibernate as JPA 1.0 provider, you can escape a reserved keyword by enclosing it within backticks:

@Column(name="`open`")

This is the syntax inherited from Hibernate Core:

5.4. SQL quoted identifiers

You can force Hibernate to quote an identifier in the generated SQL by enclosing the table or column name in backticks in the mapping document. Hibernate will use the correct quotation style for the SQL Dialect. This is usually double quotes, but the SQL Server uses brackets and MySQL uses backticks.

<class name="LineItem" table="`Line Item`">
    <id name="id" column="`Item Id`"/><generator class="assigned"/></id>
    <property name="itemNumber" column="`Item #`"/>
    ...
</class>

In JPA 2.0, the syntax is standardized and becomes:

@Column(name="\"open\"")

References

Related questions

Upvotes: 162

Ahmed Ashour
Ahmed Ashour

Reputation: 5549

There is also another option: hibernate.auto_quote_keyword

which

Specifies whether to automatically quote any names that are deemed keywords.

<property name="hibernate.auto_quote_keyword" value="true" />

Yaml

spring:
  jpa:
    properties:
      hibernate:
        auto_quote_keyword: true

Upvotes: 13

Vlad Mihalcea
Vlad Mihalcea

Reputation: 153800

Manually escaping the reserved keywords

If you are using JPA, you can escape with double quotes:

@Column(name = "\"open\"")

If you're using Hibernate native API, then you can escape them using backticks:

@Column(name = "`open`")

Automatically escaping reserved keywords

If you want to automatically escape reserved keywords, you can set to true the Hibernate-specific hibernate.globally_quoted_identifiers configuration property:

<property
    name="hibernate.globally_quoted_identifiers"
    value="true"
/>

Yaml format

spring:
  jpa:
    properties:
      hibernate:
        globally_quoted_identifiers: true

Upvotes: 31

Rafiek
Rafiek

Reputation: 1474

Had the same problem, but with a tablename called Transaction. If you set

hibernate.globally_quoted_identifiers=true

Then all database identifiers will be quoted.

Found my answer here Special character in table name hibernate giving error

And found all available settings here https://docs.jboss.org/hibernate/orm/5.2/userguide/html_single/appendices/Configurations.html

Could not find better docs for this though.

In my case the setting was in my Spring properties file. As mentioned in the comments, it could also be in other, hibernate related, configuration files.

Upvotes: 72

wmnitin
wmnitin

Reputation: 3427

@Column(name="\"open\"")

This will work for sure, Same problem happened with me, when I was learning hibernate.

Upvotes: 15

Neil Stockton
Neil Stockton

Reputation: 11531

Some JPA implementations (e.g the one I use, DataNucleus) automatically quote the identifier for you, so you never get this.

Upvotes: 3

Raman
Raman

Reputation: 210

If you use as shown below it should work

@Column(name="[order]")
private int order;

Upvotes: 17

Bozho
Bozho

Reputation: 597114

No - change the column name.

This is database-specific, and you just can't create such a column. After all hibernate finally sends DDL to the database. If you can't create a valid DDL with this column name, this means hibernate can't as well. I don't think quoting would solve the issue even if you are writing the DDL.

Even if you somehow succeed to escape the name - change it. It will work with this database, but won't work with another.

Upvotes: 3

Related Questions