[
https://issues.apache.org/jira/browse/DERBY-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583450#action_12583450
]
Bryan Pendleton commented on DERBY-3576:
----------------------------------------
> better to get rid of them. Introducing them later will take very little
> effort,
> and we also get the possibility of a discussion on whether they are required
> or not.
I agree. I looked more closely at derby-3576-1b-enginelob_interface.diff and it
looks excellent. I see no reason to have the empty interfaces until we are ready
to use them.
Thanks for the follow-up, Kristian.
> 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.
