db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dibyendu Majumdar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3351) Implement a Pluggable Storage Engine Architecture in Derby
Date Mon, 28 Jan 2008 21:59:35 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563307#action_12563307
] 

Dibyendu Majumdar commented on DERBY-3351:
------------------------------------------

> And the upshot of this is that today all the modules in the store are pluggable. :-)
One can implement a different store under Derby today! 

It makes my life easier that Derby was engineered to have this separation of layers.
Do you know if anyone has actually implemented a different Store for Derby? It would greatly
help to know what issues they faced.

> 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.


Mime
View raw message