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

Implement a Pluggable Storage Engine Architecture in Derby

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Services, SQL, Store
    • Urgency:
      Normal

      Description

      My aim is to create a pluggable storage engine architecture for Derby, so that the default store implementation can be replaced with alternative storage engines. I have created my own storage engine which I would like to use with Derby's SQL layer, so that is a motivation. But I also think that this will benefit the community, and could lead to a pluggable storage engine architecture similar to that of MySQL.

      I am not yet sure where the storage engine boundary should lie. I would welcome input in this area.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                dibyendumajumdar Dibyendu Majumdar
              • Votes:
                1 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated: