[
https://issues.apache.org/jira/browse/DERBY-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563302#action_12563302
]
Dibyendu Majumdar commented on DERBY-3351:
------------------------------------------
> I discussed this on the mailing last about a year ago, I'll look for the
> links.
I assume you are referring to DERBY-2490.
I think that in order to have a "clean API", we would need to look closely at
dependencies that the Store has on the rest of Derby, as well as the
dependencies that exist between the higher language layer and Store.
The transaction management area is obviously one of those areas - thank you for
pointing that out.
At present, I am simply gathering information and trying to understand how best
to go about with this, so any pointers are useful. It may well be that this
overall task will end up having several sub-tasks, one of which will be
DERBY-2490.
> 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.
