db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4590) You can drop a file-system database from a directory named "memory"
Date Thu, 18 Mar 2010 15:26:27 GMT

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

Kristian Waagan updated DERBY-4590:
-----------------------------------

    Attachment: derby-4590-1a-disallow_drop_properly.diff

Attaching a very simple fix for this bug. There isn't a general problem allowing one to delete
on-disk databases - the database name has to start with "memory" to be able to trigger the
bug.
I'm not sure if this catches all corner-cases, but it will hopefully do. We are already using
the remove service root functionality for on-disk databases internally, so we cannot disable
it.

I'll run the regression tests to be sure, but hopefully this change shouldn't cause any trouble.
I plan to commit it tomorrow. 

> You can drop a file-system database from a directory named "memory"
> -------------------------------------------------------------------
>
>                 Key: DERBY-4590
>                 URL: https://issues.apache.org/jira/browse/DERBY-4590
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Services, Store
>    Affects Versions: 10.6.0.0
>            Reporter: Kim Haase
>            Assignee: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-4590-1a-disallow_drop_properly.diff
>
>
> With both the embedded and network client drivers, it is possible to create a file-system
database and drop it, if you put it in a directory named "memory". 
> I found this out by accident when I accidentally typed "memory/mydb" instead of "memory:mydb"
to create an in-memory database.
> If you call the directory something other than "memory", you can't drop the db:
> ij> connect 'jdbc:derby://localhost:1527/subdir/mycdb;create=true';
> ij> create table t(c int);
> 0 rows inserted/updated/deleted
> ij> connect 'jdbc:derby://localhost:1527/subdir/mycdb;drop=true';
> ERROR XBM0I: DERBY SQL error: SQLCODE: -1, SQLSTATE: XBM0I, SQLERRMC: Directory subdir/mycdb
cannot be removed.
> But if you do exactly the same thing specifying "memory", the drop succeeds:
> ij> connect 'jdbc:derby://localhost:1527/memory/mycdb;create=true';
> ij> create table t(c int);
> 0 rows inserted/updated/deleted
> ij> connect 'jdbc:derby://localhost:1527/memory/mycdb;drop=true';
> ERROR 08006: DERBY SQL error: SQLCODE: -1, SQLSTATE: 08006, SQLERRMC: Database 'memory/mycdb'
dropped.
> When you do this, the "memory" directory continues to exist, but the database directory
under it is removed.
> Here are similar examples using the embedded driver:
> ij>  connect 'jdbc:derby:subdir/mydb;create=true';
> ij> create table t(c int);
> 0 rows inserted/updated/deleted
> ij> connect 'jdbc:derby:subdir/mydb;drop=true';
> ERROR XBM0I: Directory subdir/mydb cannot be removed.
> ij> connect 'jdbc:derby:memory/mydb;create=true';
> ij> create table t(c int);
> 0 rows inserted/updated/deleted
> ij> connect 'jdbc:derby:memory/mydb;drop=true';
> ERROR 08006: Database 'memory/mydb' dropped.
> Some part of Derby seems to think you actually created an in-memory database, although
you did not.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message