Junit HSQLDB - 用户缺少未找到的权限或对象 - THIS_.oh-ordnbr

Ram*_*ian 8 hsqldb spring-junit

当我的列名包含连字符" - "时,我收到异常

    Entity : this is the entity name.
    @Entity
    @Table(name = "RequestHeader")
    public class RequestHeader implements Serializable { 
    ....
    ....    
    @Column(name = "`oh-ordnbr`")
    private Integer ohOrdnbr;
Run Code Online (Sandbox Code Playgroud)

架构定义:这是架构创建的查询.

    CREATE MEMORY TABLE PUB.REQUESTHEADER(
           REQUESTID INTEGER,
           IMUSERID INTEGER,
           REQUESTDATE DATE,
           REQUESTTIME INTEGER,
           REQUESTSTATUS VARCHAR(19),
           REQUESTTYPE VARCHAR(22),
           HEADERINSTRUCTIONS VARCHAR(5150),
           DATEFORMAT VARCHAR(20),
           TIMEFORMAT VARCHAR(20),
           LANGUAGEID INTEGER,
           "OH-ORDNBR" INTEGER,
           "OH-TRCNSTAMP" INTEGER,
           ISPICKUPLIST BIT(1),
           CONSTRAINT "RQH-1" PRIMARY KEY(REQUESTID)
     );
Run Code Online (Sandbox Code Playgroud)

错误如下:

Exception Stack: Error message which I have received by running the Junit.
Caused by: org.hsqldb.HsqlException: user lacks privilege or object not found: THIS_.oh-ordnbr
at org.hsqldb.error.Error.error(Unknown Source)
at org.hsqldb.error.Error.error(Unknown Source)
at org.hsqldb.ExpressionColumn.checkColumnsResolved(Unknown Source)
at org.hsqldb.QueryExpression.resolve(Unknown Source)
at org.hsqldb.ParserDQL.compileCursorSpecification(Unknown Source)
at org.hsqldb.ParserCommand.compilePart(Unknown Source)
at org.hsqldb.ParserCommand.compileStatement(Unknown Source)
at org.hsqldb.Session.compileStatement(Unknown Source)
at org.hsqldb.StatementManager.compile(Unknown Source)
at org.hsqldb.Session.execute(Unknown Source)
Run Code Online (Sandbox Code Playgroud)

有人可以帮我解决这个问题吗?

Rud*_*Est 10

究其原因,找不到对象的错误是哦,ordnbr列定义为区分大小写(这是因为你把它周围的双引号)的事实.

您有两种可能的解决方案:

  1. 不要在SQL中使用破折号(连字符).无论如何,这是不好的做法,而是使用下划线.
  2. 更新JPA注释如下:

      @Column(name = "`OH-ORDNBR`")
      private Integer ohOrdnbr;
    
    Run Code Online (Sandbox Code Playgroud)

我强烈建议使用下划线而不是破折号,你永远不会知道使用第二种解决方案时JPA实现可能有什么奇怪之处.