You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2012/10/02 00:09:07 UTC

[jira] [Assigned] (DERBY-3351) Implement a Pluggable Storage Engine Architecture in Derby

     [ 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