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 "Kim Haase (JIRA)" <ji...@apache.org> on 2010/04/22 17:09:50 UTC
[jira] Resolved: (DERBY-4525) Document the in-memory storage back
end
[ https://issues.apache.org/jira/browse/DERBY-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase resolved DERBY-4525.
------------------------------
Issue & fix info: (was: [Patch Available])
Resolution: Fixed
After getting verbal okay (thanks, Kristian), committed patch DERBY-4525-3.diff to documentation trunk at revision 936885.
> 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
>
> Attachments: DERBY-4525-2.diff, DERBY-4525-2.stat, DERBY-4525-2.zip, DERBY-4525-3.diff, DERBY-4525-3.zip, DERBY-4525.diff, DERBY-4525.stat, DERBY-4525.zip
>
>
> 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.