You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/09/25 23:26:34 UTC

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

    [ https://issues.apache.org/jira/browse/DERBY-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148337#comment-14148337 ] 

ASF subversion and git services commented on DERBY-6662:
--------------------------------------------------------

Commit 1627671 from [~myrna] in branch 'code/trunk'
[ https://svn.apache.org/r1627671 ]

DERBY-6662; DatabaseMetaData.usesLocalFiles() returns true for in-memory databases
   Making the usesLocalFiles and usesLocalFilePerTable method return false if it's a memory database and add a test.

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