org.hibernate.exception.SQLGrammarException: could not execute statement

最新推荐文章于 2024-09-09 18:04:04 发布
最新推荐文章于 2024-09-09 18:04:04 发布
阅读量1w 收藏 2
点赞数 5
分类专栏： ssh 文章标签： ssh mysql
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/jamesgosling_zcc/article/details/46474305
版权

   今天，我在整合SSH框架的时候，报了一个这样的错误，如下：

org.hibernate.exception.SQLGrammarException: could not execute statement
at org.hibernate.exception.internal.SQLExceptionTypeDelegate.convert(SQLExceptionTypeDelegate.java:80)
at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:49)
at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:126)
at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:112)
at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:211)
at org.hibernate.id.insert.AbstractSelectingDelegate.performInsert(AbstractSelectingDelegate.java:61)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:3032)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:3558)
at org.hibernate.action.internal.EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:98)
at org.hibernate.engine.spi.ActionQueue.execute(ActionQueue.java:492)
at org.hibernate.engine.spi.ActionQueue.addResolvedEntityInsertAction(ActionQueue.java:197)
at org.hibernate.engine.spi.ActionQueue.addInsertAction(ActionQueue.java:181)
at org.hibernate.engine.spi.ActionQueue.addAction(ActionQueue.java:216)
at org.hibernate.event.internal.AbstractSaveEventListener.addInsertAction(AbstractSaveEventListener.java:324)
at org.hibernate.event.internal.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:288)
at org.hibernate.event.internal.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:194)
at org.hibernate.event.internal.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:125)
at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:209)
at org.hibernate.event.internal.DefaultSaveEventListener.saveWithGeneratedOrRequestedId(DefaultSaveEventListener.java:55)
at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:194)
at org.hibernate.event.internal.DefaultSaveEventListener.performSaveOrUpdate(DefaultSaveEventListener.java:49)
at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:90)
at org.hibernate.internal.SessionImpl.fireSave(SessionImpl.java:715)
at org.hibernate.internal.SessionImpl.save(SessionImpl.java:707)
at org.hibernate.internal.SessionImpl.save(SessionImpl.java:702)
at com.ssh.dao.OrderDAOImpl.addOrder(OrderDAOImpl.java:26)
at com.ssh.dao.OrderDAOImpl$$FastClassBySpringCGLIB$$45913013.invoke(<generated>)
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:717)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99)
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:281)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99)
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:281)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:653)
at com.ssh.dao.OrderDAOImpl$$EnhancerBySpringCGLIB$$22e27fc5.addOrder(<generated>)
at com.ssh.test.OrderTest.test(OrderTest.java:23)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ORDER (USERID, ROOMID) values (1, 1)' at line 1
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1054)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4190)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4122)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2570)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2731)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2818)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2157)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2460)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2377)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2361)
at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:105)
at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:208)
... 61 more



     于是我在网上查找了一下原因，结果发现是因为我的数据库表名用了MySQL关键字，表名和列名不能是MySQL关键字。MySQL关键字如下：

ADD ALL ALTER
ANALYZE AND AS
ASC ASENSITIVE BEFORE
BETWEEN BIGINT BINARY
BLOB BOTH BY
CALL CASCADE CASE
CHANGE CHAR CHARACTER
CHECK COLLATE COLUMN
CONDITION CONNECTION CONSTRAINT
CONTINUE CONVERT CREATE
CROSS CURRENT_DATE CURRENT_TIME
CURRENT_TIMESTAMP CURRENT_USER CURSOR
DATABASE DATABASES DAY_HOUR
DAY_MICROSECOND DAY_MINUTE DAY_SECOND
DEC DECIMAL DECLARE
DEFAULT DELAYED DELETE
DESC DESCRIBE DETERMINISTIC
DISTINCT DISTINCTROW DIV
DOUBLE DROP DUAL
EACH ELSE ELSEIF
ENCLOSED ESCAPED EXISTS
EXIT EXPLAIN FALSE
FETCH FLOAT FLOAT4
FLOAT8 FOR FORCE
FOREIGN FROM FULLTEXT
GOTO GRANT GROUP
HAVING HIGH_PRIORITY HOUR_MICROSECOND
HOUR_MINUTE HOUR_SECOND IF
IGNORE IN INDEX
INFILE INNER INOUT
INSENSITIVE INSERT INT
INT1 INT2 INT3
INT4 INT8 INTEGER
INTERVAL INTO IS
ITERATE JOIN KEY
KEYS KILL LABEL
LEADING LEAVE LEFT
LIKE LIMIT LINEAR
LINES LOAD LOCALTIME
LOCALTIMESTAMP LOCK LONG
LONGBLOB LONGTEXT LOOP
LOW_PRIORITY MATCH MEDIUMBLOB
MEDIUMINT MEDIUMTEXT MIDDLEINT
MINUTE_MICROSECOND MINUTE_SECOND MOD
MODIFIES NATURAL NOT
NO_WRITE_TO_BINLOG NULL NUMERIC
ON OPTIMIZE OPTION
OPTIONALLY OR ORDER
OUT OUTER OUTFILE
PRECISION PRIMARY PROCEDURE
PURGE RAID0 RANGE
READ READS REAL
REFERENCES REGEXP RELEASE
RENAME REPEAT REPLACE
REQUIRE RESTRICT RETURN
REVOKE RIGHT RLIKE
SCHEMA SCHEMAS SECOND_MICROSECOND
SELECT SENSITIVE SEPARATOR
SET SHOW SMALLINT
SPATIAL SPECIFIC SQL
SQLEXCEPTION SQLSTATE SQLWARNING
SQL_BIG_RESULT SQL_CALC_FOUND_ROWS SQL_SMALL_RESULT
SSL STARTING STRAIGHT_JOIN
TABLE TERMINATED THEN
TINYBLOB TINYINT TINYTEXT
TO TRAILING TRIGGER
TRUE UNDO UNION
UNIQUE UNLOCK UNSIGNED
UPDATE USAGE USE
USING UTC_DATE UTC_TIME
UTC_TIMESTAMP VALUES VARBINARY
VARCHAR VARCHARACTER VARYING
WHEN WHERE WHILE
WITH WRITE X509
XOR YEAR_MONTH ZEROFILL


Jochen_z
关注
专栏目录
could not execute statement;ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ORA-00001
csdn9228的博客
07-06 1892
在SSH框架中报这样的错误。 错误原因在于原先创建了表，后来觉的不够用，添加了新的列，导致新添加的列与表中的映射关系出现数据类型不对应，从而插入失败。备份数据表，删除让ssh建立新的表，或者重新匹配xxxxx.hbm.xml对应映射关系，注意映射与实体类一一对应的关系。 ...
could not execute
11-07
could not execute:bad executable format(win32 error 193) 下了一个实现MD5的代码,编译时没有错误,但是执行的时候却提示:could not execute:bad executable format(win32 error 193)
org.springframework.dao.PessimisticLockingFailureException: could not execute statement； SQL [n/a]；
最新发布
m0_51771176的博客
09-09 350
这个异常 PessimisticLockingFailureException 通常发生在使用乐观锁或悲观锁时，当尝试更新或删除数据时发生了并发冲突。假设你正在使用 Spring Boot 或 Spring Framework，你可以使用事务管理来确保整个操作在一个事务中完成。如果你的应用已经使用了乐观锁，可以考虑在删除操作中加入乐观锁字段，例如 version 字段。添加乐观锁机制：如果适用，可以考虑使用乐观锁来解决并发问题。使用事务管理：确保整个操作在一个事务中完成。
[已解决]org.hibernate.exception.SQLGrammarException: could not execute statement
热门推荐
saimer1220的博客
05-28 2万+
第一次写问题记录，在网上找了许久但还没解决 下面是各个文件的代码： <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://www.hibernate.org/dtd/hibernate-mapping-3.0.dtd"> <!-- 1配置类和表对应
Hibernate报错org.hibernate.exception.SQLGrammarException: could not execute statement
qq_32859273的博客
02-02 3153
Hibernate 5.2 + MySQL 5.5 今天在学习Hibernate的第一个例子时出现了许多问题： 1、org.hibernate.MappingException: Unknown entity 第一个问题产生的原因是视频中老师的Hibernate版本3.x，而我自己用的为Hibernate 5.x，两个版本创建服务对象和会话工厂对象的方法的写法不一样，因此报了这个错误。
hibernate创建数据库时报错：org.hibernate.exception.SQLGrammarException: could not execute statement
qq_36443497的博客
08-08 8137
在我使用hibernate实现映射一对多的关联时，报出如下错误： org.hibernate.exception.SQLGrammarException: could not execute statement at org.hibernate.exception.internal.SQLExceptionTypeDelegate.convert(SQLExceptionTypeDelegat
org.hibernate.exception.SQLGrammarException: could not execute statement错误
TN1954的博客
07-23 1028
错误详情如下： 错误原因： hibernate.cfg.xml配置文件中的hibernate所使用的数据库方言信息 &lt;property name="hibernate.dialect"&gt;org.hibernate.dialect.MySQLDialect&lt;/property&gt; 该操作后会生成一条SQL语句，该语句不能被解析导致的。 解决方案： 将该条语句...
nested exception is org.hibernate.exception.SQLGrammarException: could not execute statement
08-23
这个错误是由 Hibernate 引起的，它表明在执行 SQL 语句时遇到了语法错误。通常情况下，这种错误是由于数据库模式定义与实际执行的 SQL 语句不匹配所导致的。 为了解决这个问题，你可以考虑以下几个步骤： 1. 检查...
prg.hibernate.exception.sQLGrammarException: could not execute statement
08-14
回答: prg.hibernate.exception.sQLGrammarException: could not execute statement一个Hibernate的异常，表示无法执行SQL语句。根据引用和引用的错误消息，这个异常是因为SQL语法错误导致的。具体来说，错误消息中...
org.hibernate.exception.SQLGrammarException: could not execute statement [Unknown column 'SNAME' in 'field list'] [insert into erp_product (SNAME,PRICE,QTY) values (?,?,?)]
04-23
这看起来像是一个数据库查询错误，具体原因可能是数据库模式的变化，导致查询语句无法正确地执行。您需要检查数据库模式中是否存在名为SNAME的列，并检查查询语句是否正确地引用了该列。如果存在问题，建议您修改该...
严重: 在路径为/oasshapi2023springmvc的上下文中，Servlet[dispatcher]的Servlet.service（）引发了具有根本原因的异常Request processing failed: org.hibernate.exception.SQLGrammarException: could not execute statement [Unknown column 'SNAME' in 'field list'] [insert into erp_product (SNAME,PRICE,QTY) values (?,?,?)] java.sql.SQLSyntaxErrorException: Unknown column 'SNAME' in 'field list'
04-23
很抱歉听到你遇到了这样的问题。根据你的描述，可能是因为在数据库的表中缺少字段 'SNAME'，导致出现了SQL语法异常。建议你检查一下表结构，看看是否有漏掉该字段的定义。如果需要进一步的帮助，可以提供更多的信息...
Hibernate异常总结：org.hibernate.exception.SQLGrammarException: could not execute statement
种一棵树最好的时间是十年前，其次是现在。
04-23 3761
本质原因：配置的Java Bean,由Hibernate自动产生的SQL语句中有语法错误 原因如下： 　　情况1.存在字段名/表名与数据库关键字冲突 　　情况2.MySQL5.0以后与MySQL5.0以前事务引擎InnoDB配置微妙不同 //MySQL 5.0之后【engine = InnoDB】 &lt;property name="hibernate.dialect"&gt;org.h...
【MySQL】报错：org.hibernate.exception.SQLGrammarException: could not execute statement
winrh的博客
04-21 757
在学映射多对一时，因为表名起为order而报错（是MySQL关键字）： Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL serv...
错误:org.hibernate.exception.SQLGrammarException: could not execute
天龙的博客
12-02 2614
于Hibernate的应用程序的开发过程中，通过Hibernate操作数据库时，在程序执行过程中出现了SQL Grammer Exception,Could not execute JDBC batch update的提示信息。遇到此类问题确实让人感觉摸不着头脑（尤其是第一次遇到），不过解决此类问题并不需要大动干戈地大规模修改代码，也不需要做更改数据库连接方式这样动用牛刀的事。问题的来源还在于细节...
org.hibernate.exception.SQLGrammarException:could not execute statement
The_climber的博客
10-12 567
SQL语法异常，思路：从映射文件和配置文件中找错误 查询映射文件时发现实体类属性和数据库表字段不是一一对应关系 将字段对应即可，都改为cust_level ...
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值