db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4066) Allow functions/procedures to take Blob/Clob arguments
Date Mon, 02 Mar 2009 22:00:56 GMT

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

Rick Hillegas updated DERBY-4066:
---------------------------------

    Attachment: derby-4066-01-ag-enableLobArgs.diff

Attaching derby-4066-01-ag-enableLobArgs.diff. However, this patch is not ready for committing.
LOB return values work across the network. However, LOB arguments (both input and output)
do not work across the network. I am not going to put any more effort into this issue for
10.5.

> Allow functions/procedures to take Blob/Clob arguments
> ------------------------------------------------------
>
>                 Key: DERBY-4066
>                 URL: https://issues.apache.org/jira/browse/DERBY-4066
>             Project: Derby
>          Issue Type: New Feature
>          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