[jira] [Resolved] (DERBY-6662) DatabaseMetaData.usesLocalFiles() returns true for in-memory databases

["Myrna van Lunteren (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren resolved DERBY-6662.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 10.12.0.0
                   10.11.1.2
                   10.10.2.1

> 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
>             Fix For: 10.10.2.1, 10.11.1.2, 10.12.0.0
>
>         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)