db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4066) Allow functions/procedures to take Blob/Clob arguments
Date Fri, 28 Aug 2009 13:08:59 GMT

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

Knut Anders Hatlen commented on DERBY-4066:
-------------------------------------------

When procedures are allowed to take Blob/Clob arguments, we should also implement CallableStatement.getBlob()
and CallableStatement.getClob(), either as part of this issue or in a follow-up issue. Those
methods are not implemented on the embedded driver, see DERBY-477.

> Allow functions/procedures to take Blob/Clob arguments
> ------------------------------------------------------
>
>                 Key: DERBY-4066
>                 URL: https://issues.apache.org/jira/browse/DERBY-4066
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.4.2.0
>            Reporter: Rick Hillegas
>         Attachments: derby-4066-01-aa-enableLobArgs.diff, derby-4066-01-ab-enableLobArgs.diff,
derby-4066-01-ag-enableLobArgs.diff
>
>
> Derby objects if you try to declare a function or procedure with an argument whose type
is BLOB or CLOB. These kinds of arguments are allowed in the SQL standard and the matching
Java types are java.sql.Blob and java.sql.Clob. See the SignatureMatching.html summary attached
to DERBY-3652.
> We should lift this restriction and allow functions and procedures to take large object
arguments.

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