Mike Matrigali wrote:
From the documentation it is clear that there is no current support for
blob/clob as parameters. I always assumed that extended to return value
also. It is sort of unclear from the documentation.
Anyone know if current code was meant to support blob/clob as return value?
I think BLOB/CLOB as parameters is a different case to BLOB/CLOB as a
function's return.
As parameters Derby must create a java.sql.Blob/Clob object from the SQL
BLOB/CLOB value and since that code is in the JDBC layer, it's somewhat
hard for the language layer to do so. [Though since I think it is done
internally for triggers that use BLOB/CLOBs I think it is possible].
However for a function's return, it's the function (i.e. user code) that
creates/obtains the java.sql.Blob/Clob object so it's easier for Derby
to consume the user supplied value and convert it to a SQL BLOB/CLOB.
I looked at fixing this a while back (but forgot to add a Jira entry), I
think I was heading down the same path that Øystein has in his partial
patch, adding various methods to the DataValueFactory and SQLClob/SQLBlob.
Dan.
