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] Closed: (DERBY-3576) Merge EngineBlob and EngineClob into a single interface
Date Tue, 01 Apr 2008 09:08:27 GMT

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

Kristian Waagan closed DERBY-3576.
----------------------------------


Thanks for informing me about the problem Mamta.

I have fixed it with revision 643326 and 643328 (10.4), and you are correct the we either
need an import or use a fully qualified reference to the class. I chose the latter, since
we don't use EmbedConnection in the method signatures.

Closing the 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