db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6662) DatabaseMetaData.usesLocalFiles() returns true for in-memory databases
Date Thu, 25 Sep 2014 21:18:34 GMT

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

Myrna van Lunteren updated DERBY-6662:
--------------------------------------
    Attachment: DERBY-6662.diff

Attaching a patch which fixes this.
Also adds a test (Derby6662Test) to the memorydb._Suite.
I ran the memorydb suite and the test passed in the environment with the fix, but failed without.
I will commit this shortly.

> 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
>
>
> 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)

Mime
View raw message