-
15. Re: Apache Derby as cache store behaves different with 5.2.1.Final release
dex80526 Mar 18, 2013 1:17 PM (in response to nadirx)Here is what I got with my configuration (I am on 10.8 too):
>>>
ij> show tables;
TABLE_SCHEM |TABLE_NAME |REMARKS
------------------------------------------------------------------------
SYS |SYSALIASES |
SYS |SYSCHECKS |
SYS |SYSCOLPERMS |
SYS |SYSCOLUMNS |
SYS |SYSCONGLOMERATES |
SYS |SYSCONSTRAINTS |
SYS |SYSDEPENDS |
SYS |SYSFILES |
SYS |SYSFOREIGNKEYS |
SYS |SYSKEYS |
SYS |SYSPERMS |
SYS |SYSROLES |
SYS |SYSROUTINEPERMS |
SYS |SYSSCHEMAS |
SYS |SYSSEQUENCES |
SYS |SYSSTATEMENTS |
SYS |SYSSTATISTICS |
SYS |SYSTABLEPERMS |
SYS |SYSTABLES |
SYS |SYSTRIGGERS |
SYS |SYSVIEWS |
SYSIBM |SYSDUMMY1 |
SA |ISPN_STRING_TABLE_keychain |
23 rows selected
ij> select * from SA.ISPN_STRING_TABLE_keychain;
ERROR 42X05: Table/View 'SA.ISPN_STRING_TABLE_KEYCHAIN' does not exist.
But, this does not happen to 5.1.* code.
Thanks.
-
16. Re: Apache Derby as cache store behaves different with 5.2.1.Final release
dex80526 Mar 18, 2013 1:52 PM (in response to dex80526)WOW! I found the issue. I think the changes made in 5.2.1 in table creation, I believe, causes the table name case sensitive.
If I use all UPPER case for my cache name in the above sample, I was able to connect and select element from the table using 'ij'. Otherwise, it fails. Apache Derby convert all unquoted string into UPPER case, I think.
This cause backword capatibility problem for the case stores created with previous versions.
-
17. Re: Apache Derby as cache store behaves different with 5.2.1.Final release
dex80526 Mar 18, 2013 3:11 PM (in response to nadirx)Hey Trisan:
I figured out the root cause. In 5.2, you used the quoted table name in creating tables (TableManipulation.java), which makes table name case sensitive (see my other posts).
In previous version, the table name is not quoted and hence case insensitive.
This will cause backward compatibility issue.