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 "Francois Orsini (JIRA)" <ji...@apache.org> on 2008/09/03 23:15:44 UTC

[jira] Commented: (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:comment-tabpanel&focusedCommentId=12628139#action_12628139 ] 

Francois Orsini commented on DERBY-3351:
----------------------------------------

Adding the link below as a note as it would be great to have a pluggable storage cookbook for Derby.
http://forge.mysql.com/wiki/MySQL_Internals_Custom_Engine

> Implement a Pluggable Storage Engine Architecture in Derby
> ----------------------------------------------------------
>
>                 Key: DERBY-3351
>                 URL: https://issues.apache.org/jira/browse/DERBY-3351
>             Project: Derby
>          Issue Type: New Feature
>          Components: Services, SQL, Store
>            Reporter: Dibyendu Majumdar
>            Assignee: Dibyendu Majumdar
>
> 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.
-
You can reply to this email to add a comment to the issue online.