db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3576) Merge EngineBlob and EngineClob into a single interface
Date Tue, 01 Apr 2008 05:24:24 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584009#action_12584009
] 

Mamta A. Satoor commented on DERBY-3576:
----------------------------------------

Kristian, one minor thing I noticed is javadoc gives following error on our internal IBM machines.
Could it be because javadoc does not know where to find the class EmbedConnection? It seems
strange but do we need to have an import of this class in order for javadoc to find the link
to it?
Docs:
  Failed with following errors. Check details in docs.txt
  [javadoc] C:\nightlies\main\src\opensource\java\engine\org\apache\derby\iapi\jdbc\EngineLOB.java:46:
warning - Tag @link: reference not found: EmbedConnection#getLobMapping
  [javadoc] C:\nightlies\main\src\opensource\java\engine\org\apache\derby\iapi\jdbc\EngineLOB.java:46:
warning - Tag @link: reference not found: EmbedConnection#getLobMapping
	  [javadoc] 2 warnings


> 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