[
https://issues.apache.org/jira/browse/DERBY-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701242#action_12701242
]
Knut Anders Hatlen commented on DERBY-4171:
-------------------------------------------
One potential problem with (2) is that in a multi-user environment, one user
can create an in-memory database with the same path as a known, unbooted
disk-based database, and thereby prevent other users from booting the
disk-based database.
Which compatibility issues would we see when moving from (1) to (2) that we
won't see when moving from the current situation to (2)?
> Connections to on-disk db go to in-memory db if in-memory db with same name
> is booted
> -------------------------------------------------------------------------------------
>
> Key: DERBY-4171
> URL: https://issues.apache.org/jira/browse/DERBY-4171
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.5.1.1
> Reporter: Knut Anders Hatlen
> Attachments: derby-4171-1a-fix.diff
>
>
> When an in-memory database has been booted, subsequent attempts to connect to
> an ordinary (on-disk) database with the same name as the in-memory database
> will connect to the in-memory db.
> ij version 10.5
> ij> connect 'jdbc:derby:memory:MyDB;create=true'; -- with subprotocol memory
> ij> create table t (x varchar(30));
> 0 rows inserted/updated/deleted
> ij> insert into t values 'This is the in-memory backend';
> 1 row inserted/updated/deleted
> ij> connect 'jdbc:derby:MyDB;create=true'; --without subprotocol memory,
> should create disk db
> WARNING 01J01: Database 'MyDB' not created, connection made to existing
> database instead.
> ij(CONNECTION1)> select * from t;
> X
> ------------------------------
> This is the in-memory backend
> 1 row selected
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
