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 "Kristian Waagan (JIRA)" <ji...@apache.org> on 2008/03/28 10:30:24 UTC
[jira] Commented: (DERBY-3576) Merge EngineBlob and EngineClob into
a single interface
[ https://issues.apache.org/jira/browse/DERBY-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582950#action_12582950 ]
Kristian Waagan commented on DERBY-3576:
----------------------------------------
suites.All ran without related failures on 10.4:
Tests run: 10340, Failures: 1, Errors: 0
The failed test was the ManagementMBeanTest.testStartStopManagementFromApplication test.
> Merge EngineBlob and EngineClob into a single interface
> -------------------------------------------------------
>
> Key: DERBY-3576
> URL: https://issues.apache.org/jira/browse/DERBY-3576
> Project: Derby
> Issue Type: Sub-task
> Components: Network Server
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments: derby-3576-1a-enginelob_interface.diff, derby-3576-1a-enginelob_interface.stat
>
>
> There are currently two identical interfaces called EngineBlob and EngineClob.
> Merging these into a single interface would simplify some of the code handling Blob and Clob in the network server, and it also allows a leaner implementation of a stored procedure freeing LOB locators without knowing if the locator represents a Blob or a Clob.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.