db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4932) Move the StringColumnVTI to the public api
Date Mon, 06 Dec 2010 22:56:09 GMT

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

Dag H. Wanvik commented on DERBY-4932:
--------------------------------------

> I think that we should have exposed VTITemplate when we introduced
> user-written table functions. That class was described in the
> Cloudscape 3.5 Developer's Guide.  A future enhancement would be to
> write a more extensive tutorial on how to write table functions.

Both seem good. +1



> Move the StringColumnVTI to the public api
> ------------------------------------------
>
>                 Key: DERBY-4932
>                 URL: https://issues.apache.org/jira/browse/DERBY-4932
>             Project: Derby
>          Issue Type: Improvement
>          Components: Javadoc, SQL, Tools
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>            Priority: Minor
>         Attachments: derby-4932-01-aa-exposeVTITemplate.diff, derby-4932-02-aa-moveStringColumnVTI.diff
>
>
> I have found StringColumnVTI to be a very useful class for removing the drudgery of writing
a table function. I would like to move it to move it into the package with the other public
vti machinery and then expose it as part of Derby's public api.

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