db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (DERBY-3351) Implement a Pluggable Storage Engine Architecture in Derby
Date Mon, 01 Oct 2012 22:09:07 GMT

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

Kathey Marsden reassigned DERBY-3351:

    Assignee:     (was: Dibyendu Majumdar)

Unassigning per Dibyendu's request.

> Implement a Pluggable Storage Engine Architecture in Derby
> ----------------------------------------------------------
>                 Key: DERBY-3351
>                 URL: https://issues.apache.org/jira/browse/DERBY-3351
>             Project: Derby
>          Issue Type: Improvement
>          Components: Services, SQL, Store
>            Reporter: Dibyendu Majumdar
>              Labels: derby_triage10_10
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message