You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2010/06/01 19:03:40 UTC
[jira] Created: (CONNECTORS-39) Database abstraction layer does not
abstract from transactions
Database abstraction layer does not abstract from transactions
--------------------------------------------------------------
Key: CONNECTORS-39
URL: https://issues.apache.org/jira/browse/CONNECTORS-39
Project: Lucene Connector Framework
Issue Type: Improvement
Components: Framework core
Reporter: Karl Wright
The database abstraction layer in LCF does not permit someone to abstract from transaction management. That responsibility is delegated to a different class, which presumes that transaction management is not database-type dependent. Unfortunately, this is not the case.
A better code structure would involve creating an abstract base class that performed the transaction management and caching, and causing all database implementations to be derived from it. Then, abstract methods for transaction begin and end could be readily defined.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CONNECTORS-39) Database abstraction layer does
not abstract from transactions
Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONNECTORS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Wright resolved CONNECTORS-39.
-----------------------------------
Resolution: Fixed
> Database abstraction layer does not abstract from transactions
> --------------------------------------------------------------
>
> Key: CONNECTORS-39
> URL: https://issues.apache.org/jira/browse/CONNECTORS-39
> Project: Lucene Connector Framework
> Issue Type: Improvement
> Components: Framework core
> Reporter: Karl Wright
> Assignee: Karl Wright
>
> The database abstraction layer in LCF does not permit someone to abstract from transaction management. That responsibility is delegated to a different class, which presumes that transaction management is not database-type dependent. Unfortunately, this is not the case.
> A better code structure would involve creating an abstract base class that performed the transaction management and caching, and causing all database implementations to be derived from it. Then, abstract methods for transaction begin and end could be readily defined.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CONNECTORS-39) Database abstraction layer does
not abstract from transactions
Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONNECTORS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Wright reassigned CONNECTORS-39:
-------------------------------------
Assignee: Karl Wright
> Database abstraction layer does not abstract from transactions
> --------------------------------------------------------------
>
> Key: CONNECTORS-39
> URL: https://issues.apache.org/jira/browse/CONNECTORS-39
> Project: Lucene Connector Framework
> Issue Type: Improvement
> Components: Framework core
> Reporter: Karl Wright
> Assignee: Karl Wright
>
> The database abstraction layer in LCF does not permit someone to abstract from transaction management. That responsibility is delegated to a different class, which presumes that transaction management is not database-type dependent. Unfortunately, this is not the case.
> A better code structure would involve creating an abstract base class that performed the transaction management and caching, and causing all database implementations to be derived from it. Then, abstract methods for transaction begin and end could be readily defined.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.