[
https://issues.apache.org/jira/browse/DERBY-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149745#comment-14149745
]
ASF subversion and git services commented on DERBY-6662:
--------------------------------------------------------
Commit 1627851 from [~myrna] in branch 'code/trunk'
[ https://svn.apache.org/r1627851 ]
DERBY-6662; DatabaseMetaData.usesLocalFiles() returns true for in-memory
databases
Adding a test case using the metadata optional tool.
> DatabaseMetaData.usesLocalFiles() returns true for in-memory databases
> ----------------------------------------------------------------------
>
> Key: DERBY-6662
> URL: https://issues.apache.org/jira/browse/DERBY-6662
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.11.1.1
> Reporter: Rick Hillegas
> Assignee: Myrna van Lunteren
> Attachments: DERBY-6662.diff, DERBY-6662.diff2
>
>
> DatabaseMetaData.usesLocalFiles() returns true for in-memory databases. And
> it also returns true for DatabaseMetaData.usesLocalFilePerTable(). The
> following script shows this:
> {noformat}
> connect 'jdbc:derby:memory:db;create=true';
> call syscs_util.syscs_register_tool( 'databaseMetaData', true );
> values usesLocalFiles();
> values usesLocalFilePerTable();
> {noformat}
> I think that these methods should return false because an in-memory database
> does not store tables in files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
