@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?
8条答案
按热度按时间g0czyy6m1#
With Hibernate as JPA 1.0 provider, you can escape a reserved keyword by enclosing it within backticks:
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.
In JPA 2.0, the syntax is standardized and becomes:
References
Related questions
rxztt3cl2#
Had the same problem, but with a tablename called
Transaction
. If you setThen 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.
qlvxas9a3#
Manually escaping the reserved keywords
If you are using JPA, you can escape with double quotes:
If you're using Hibernate native API, then you can escape them using backticks:
Automatically escaping reserved keywords
If you want to automatically escape reserved keywords, you can set to
true
the Hibernate-specifichibernate.globally_quoted_identifiers
configuration property:Yaml format
kh212irz4#
If you use as shown below it should work
b1payxdu5#
This will work for sure, Same problem happened with me, when I was learning hibernate.
oo7oh9g96#
There is also another option: hibernate.auto_quote_keyword
which
Specifies whether to automatically quote any names that are deemed keywords.
Yaml
rqdpfwrv7#
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.
lf5gs5x28#
Some JPA implementations (e.g the one I use, DataNucleus) automatically quote the identifier for you, so you never get this.