db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <j...@apache.org>
Subject [jira] Resolved: (DERBY-1285) Finish JDBC3 Blob implementation
Date Wed, 04 Jul 2007 21:43:04 GMT

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

Øystein Grøvlen resolved DERBY-1285.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0

I changing this to resolved since all methods except the CallableStatement.getBlob method
has now been implemented.  I will open another JIRA for this method.  (It is of no use to
implement this  method before DERBY-2201 is fixed)

> Finish JDBC3 Blob implementation
> --------------------------------
>
>                 Key: DERBY-1285
>                 URL: https://issues.apache.org/jira/browse/DERBY-1285
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions: 10.2.1.6
>            Reporter: Rick Hillegas
>             Fix For: 10.3.0.0
>
>
> Fill in the following methods required for JDBC3 compliance:
> - The following java.sql.CallableStatement methods:
>   * getBlob(int)
> - The following java.sql.ResultSet methods:
>   * updateBlob(int,java.sql.Blob)
>   * updateBlob(java.lang.String,java.sql.Blob)
> - The following java.sql.Blob methods:
>   * java.sql.Blob.setBytes(long,byte[])
>   * setBytes(long,byte[],int,int)
>   * getBinaryStream(long,long)
>   * setBinaryStream(long)
>   * truncate(long)

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