db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4525) Document the in-memory storage back end
Date Wed, 21 Apr 2010 22:24:50 GMT

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

Kim Haase updated DERBY-4525:
-----------------------------

    Attachment: DERBY-4525-3.diff
                DERBY-4525-3.zip

Thanks so much, Kristian, for the careful review. I'm attaching a final(?) patch, DERBY-4525-3.diff
and DERBY-4525-3.zip. I hope I have incorporated all your edits. A couple of notes:

* src/ref/rrefattrib17246.dita
In the example:
  "+<codeblock><b>jdbc:derby:toursDB;databaseName=flightsDB</b></codeblock>"
- 
  specifies two database names

Actually, this is intentional -- the description above is of what happens if you specify two
names this way. But perhaps it is an obscure enough case that it should come after the in-memory
db info -- so I swapped the order.

I hope the wording in the Tuning Guide topic is okay -- I didn't add all the supporting detail,
just changed the emphasis. Let me know if it still needs work.

I added a small section on persisting databases to the Dev Guide topic. If anyone objects,
we can change it.

I changed the wording of the note in "Derby system" (src/devguide/cdevdvlp27610.dita) slightly.


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


Mime
View raw message