Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-4525

Document the in-memory storage back end



    • Task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • Documentation
    • None


      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-3.zip
          56 kB
          Camilla Haase
        2. DERBY-4525-3.diff
          36 kB
          Camilla Haase
        3. DERBY-4525.zip
          54 kB
          Camilla Haase
        4. DERBY-4525.stat
          0.9 kB
          Camilla Haase
        5. DERBY-4525.diff
          31 kB
          Camilla Haase
        6. ASF.LICENSE.NOT.GRANTED--DERBY-4525-2.zip
          55 kB
          Camilla Haase
        7. ASF.LICENSE.NOT.GRANTED--DERBY-4525-2.stat
          0.9 kB
          Camilla Haase
        8. ASF.LICENSE.NOT.GRANTED--DERBY-4525-2.diff
          34 kB
          Camilla Haase

        Issue Links



              chaase3 Camilla Haase
              kristwaa Kristian Waagan
              0 Vote for this issue
              0 Start watching this issue