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

Kim Haase commented on DERBY-4525:
----------------------------------

Actually, that syntax was wrong -- I accidentally put a slash instead of a 
colon, which created a file-system database named myDB in the directory memory. 
I shouldn't have been able to drop it, should I? I thought drop only worked on 
in-memory databases.

The same error results if I do it right.

ij> connect 'jdbc:derby://localhost:1527/memory:myDB;create=true';
ij> connect 'jdbc:derby://localhost:1527/memory:myDB;drop=true';
ERROR 08006: DERBY SQL error: SQLCODE: -1, SQLSTATE: 08006, SQLERRMC: Database 
'memory:myDB' dropped.


> Document the in-memory storage back end
> ---------------------------------------
>
>                 Key: DERBY-4525
>                 URL: https://issues.apache.org/jira/browse/DERBY-4525
>             Project: Derby
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 10.6.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kim Haase
>             Fix For: 10.6.0.0
>
>
> The in-memory back end isn't considered experimental anymore, we have to 
> write user documentation for the feature(s).
> I'm not  sure how it should be structured, and where the content should be 
> added.
> Just as a rough cut, here are a few possible topics (I'm not sure if all 
> should be included or not):
> - documenting the new protocol name ('memory')
> - documenting the new 'drop' JDBC connection URL attribute
> - describing the limitations of the feature (all your data will be lost 
> if..., how to use it with the client driver and the data sources)
> - "advanced use" (pull dbs on disk into memory, backup in-memory dbs to disk)
> - tuning tips (there are some issues with extreme page cache sizes, maybe the 
> existing content on page size is valid)
> - known problems (nothing concrete here yet, but we have one inquiry about 
> disappearing databases - the current theory is that different class loaders 
> are used)
> Some more information is available at 
> http://wiki.apache.org/db-derby/InMemoryBackEndPrimer

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

Reply via email to