[h2] preserve capitalization of column names in returned meta data

2015-02-08 Thread Adam McMahon
Hi,

When we get the meta data of a result set, it appears that the 
capitalization of the column names is not preserved.  Is there anyway to 
preserve it the returned meta results?

-Adam

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.


[h2] Re: Need help with [42102-169] Table not found errors.

2015-02-08 Thread Duc Nguyen
Please response

On Wednesday, February 4, 2015 at 12:45:01 PM UTC+7, Duc Nguyen wrote:
>
> Hi,
>
> Our customer has reported that our application doesn't work correctly. 
> Examining the database that customer sent us, we found lots of "Table not 
> found [42102-169]" errors (I literally believe that all the errors recorded 
> by trace files are [42102-169] by counting the number of error 
> occurrences). Some sample error traces:
>
> 01-03 09:36:26 jdbc[2]: exception
> org.h2.jdbc.JdbcSQLException: Table "REVDNSINFO" not found; SQL statement:
> SELECT * FROM RevDnsInfo WHERE IpAddress='172.23.32.189' [42102-169]
> 01-03 09:36:26 jdbc[2]: exception
> org.h2.jdbc.JdbcSQLException: Table "REVDNSINFO" not found; SQL statement:
> insert into RevDnsInfo (IpAddress,IpName,InfoTime,NeedTime) values 
> ('172.23.32.189','','1969-12-31 19:00:00.000','1969-12-31 19:00:00.000') 
> [42102-169]
> 01-03 09:36:26 jdbc[2]: exception
> org.h2.jdbc.JdbcSQLException: Table "REVDNSINFO" not found; SQL statement:
> SELECT * FROM RevDnsInfo WHERE IpAddress='172.23.32.77' [42102-169]
> 01-03 09:36:26 jdbc[2]: exception
> org.h2.jdbc.JdbcSQLException: Table "REVDNSINFO" not found; SQL statement:
> insert into RevDnsInfo (IpAddress,IpName,InfoTime,NeedTime) values 
> ('172.23.32.77','','1969-12-31 19:00:00.000','1969-12-31 19:00:00.000') 
> [42102-169]
> 01-03 09:36:26 jdbc[2]: exception
> org.h2.jdbc.JdbcSQLException: Table "REVDNSINFO" not found; SQL statement:
> SELECT * FROM RevDnsInfo WHERE IpAddress='172.23.33.25' [42102-169]
> 01-03 09:36:26 jdbc[2]: exception
> org.h2.jdbc.JdbcSQLException: Table "REVDNSINFO" not found; SQL statement:
> insert into RevDnsInfo (IpAddress,IpName,InfoTime,NeedTime) values 
> ('172.23.33.25','','1969-12-31 19:00:00.000','1969-12-31 19:00:00.000') 
> [42102-169]
> 01-03 09:36:26 jdbc[2]: exception
> org.h2.jdbc.JdbcSQLException: Table "REVDNSINFO" not found; SQL statement:
> SELECT * FROM RevDnsInfo WHERE IpAddress='172.23.33.74' [42102-169]
> 01-03 09:36:26 jdbc[2]: exception
> org.h2.jdbc.JdbcSQLException: Table "REVDNSINFO" not found; SQL statement:
> insert into RevDnsInfo (IpAddress,IpName,InfoTime,NeedTime) values 
> ('172.23.33.74','','1969-12-31 19:00:00.000','1969-12-31 19:00:00.000') 
> [42102-169]
>
>
> Some information about our database connection:
> Version: Embedded H2, version 1.3.169
> URL:  jdbc:h2:/database_directory/Omnxxx;LOCK_TIMEOUT=5000(where 
> Omnxxx is database name)
> Use Connection Pool: Yes, size=256
> Use DB Schema: Yes
> Use AutoCommit: Yes
> Other configurations: No
> OS on which application is running: RedHat 5.7 x64
>
> I had done some search on both this group and Google, but found no case 
> where root cause of issue matches with the case I'm working on. There are 
> some simple troubleshooting questions that I can answer here:
> > Is the database corrupted?
> No because application was able to establish connection to DB using 
> connection URL above
> > Is the schema wrong ?
> No because our application was released years ago and there are few error 
> reports regarding SQL database issue, the schema isn't exposed to end user
> > Is connection URL correct?
> Yes
>
> Also, I noticed that while [42102-169] errors were written out to trace 
> file, there were also success queries (by checking datemodified timestamp 
> of many entries of reported tables). That means that not all executed 
> queries failed. 
> Second, for few cases that have reported with same errors, I found that 
> they are all have pretty big database, for this case database file is 
> ~400MB, for the other cases, size of h2 database files are even bigger.
>
> I'm looking for a root cause analysis, if not then just some insights, 
> probably possible causes of this "Table not found" issue (other than wrong 
> database name, empty database, incorrect schema), to further figure out the 
> steps I need to take to debug this issue from our end. 
>
> Thank you.
>

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.