JdbcSQLException in DBTrace-Logfile (Column "PRECISION" not found)

[GoogleCodeExporter]

Hello,

I found a recurrent error in the DB trace log file:

12-15 18:50:28 jdbc[3]: exception
org.h2.jdbc.JdbcSQLException: Feld "PRECISION" nicht gefunden
Column "PRECISION" not found [42122-174]
    at org.h2.message.DbException.getJdbcSQLException(DbException.java:332)
    at org.h2.message.DbException.get(DbException.java:172)
    at org.h2.message.DbException.get(DbException.java:149)
    at org.h2.jdbc.JdbcResultSet.getColumnIndex(JdbcResultSet.java:3047)
    at org.h2.jdbc.JdbcResultSet.findColumn(JdbcResultSet.java:176)
    at org.h2.bnf.context.DbContents.findColumn(DbContents.java:126)
    at org.h2.bnf.context.DbColumn.<init>(DbColumn.java:33)
    at org.h2.bnf.context.DbTableOrView.readColumns(DbTableOrView.java:98)
    at org.h2.bnf.context.DbSchema.readTables(DbSchema.java:132)
    at org.h2.bnf.context.DbContents.readContents(DbContents.java:177)
    at org.h2.server.web.WebApp.tables(WebApp.java:666)
    at org.h2.server.web.WebApp.process(WebApp.java:223)
    at org.h2.server.web.WebApp.processRequest(WebApp.java:168)
    at org.h2.server.web.WebThread.process(WebThread.java:138)
    at org.h2.server.web.WebThread.run(WebThread.java:94)
    at java.lang.Thread.run(Unknown Source)

This error is reproducible always occurred when opening the database via the 
web interface. (When opening once the exception occurs over 300 times within a 
second). In the web interface is nothing to see, the functionality is not 
compromised. When connecting from a program (using JDBC), there are no 
exceptions.

I currently use the version 1.3.174 (previously 1.3.172, 1.3.169 and 1.3.163). 
Judging by the date in the stack trace, the error has occurred also more than a 
year ago.

My operating system:
Windows 7 32-bit
Error is to reproduce also an Ubuntu VM (version 12:04 32-bit).

The error is not urgent, because the functionality is limited in any way.

best regards
Christian Kotzbauer

Original issue reported on code.google.com by adobe0815 on 15 Dec 2013 at 6:24

[GoogleCodeExporter]

Yes, this is a bug, introduced by some completely unrelated changes (moving the 
BNF classes). I tried to fix it (the fix is in the trunk).

Original comment by thomas.t...@gmail.com on 18 Dec 2013 at 9:39

• Changed state: Accepted

[GoogleCodeExporter]

Fixed in version 1.3.175

Original comment by thomas.t...@gmail.com on 18 Jan 2014 at 6:17

• Changed state: Fixed