db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-3576) Merge EngineBlob and EngineClob into a single interface
Date Sun, 30 Mar 2008 11:15:24 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan resolved DERBY-3576.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.5.0.0
                   10.4.1.0
       Derby Info:   (was: [Patch Available])

Committed 'derby-3576-1b-enginelob_interface.diff ' to trunk with revision 642707 and merged
it to the 10.4 branch with revision 642711.
Unless the ongoing discussion brings out the need for more changes, I don't expect more patches
to go in for this issue.

> 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
>             Fix For: 10.4.1.0, 10.5.0.0
>
>         Attachments: derby-3576-1a-enginelob_interface.diff, derby-3576-1a-enginelob_interface.stat,
derby-3576-1b-enginelob_interface.diff
>
>
> 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.


Mime
View raw message