Derby
  1. Derby
  2. DERBY-4525

Document the in-memory storage back end

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.6.1.0
    • Fix Version/s: 10.6.1.0
    • Component/s: Documentation
    • Labels:
      None

      Description

      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

      1. DERBY-4525.diff
        31 kB
        Kim Haase
      2. DERBY-4525.stat
        0.9 kB
        Kim Haase
      3. DERBY-4525.zip
        54 kB
        Kim Haase
      4. ASF.LICENSE.NOT.GRANTED--DERBY-4525-2.diff
        34 kB
        Kim Haase
      5. ASF.LICENSE.NOT.GRANTED--DERBY-4525-2.stat
        0.9 kB
        Kim Haase
      6. ASF.LICENSE.NOT.GRANTED--DERBY-4525-2.zip
        55 kB
        Kim Haase
      7. DERBY-4525-3.diff
        36 kB
        Kim Haase
      8. DERBY-4525-3.zip
        56 kB
        Kim Haase

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Kim Haase
              Reporter:
              Kristian Waagan
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development