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] Updated: (DERBY-2495) Create framework for calling locator related stored procedures from client
Date Tue, 03 Apr 2007 12:39:32 GMT

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

Øystein Grøvlen updated DERBY-2495:

    Attachment: blobframework_v2.diff

blobframework_v2.diff is a new version of the patch which makes sure
that calling the LOB procedures does not initiate a commit when
running in auto-commit mode.  

In addition to the earlier described changes, this version contains
the following new changes:

A      java/client/org/apache/derby/client/am/CallableLocatorProcedures.java

       For each prepared statement, the field
       isAutoCommittableStatement_ is set to false, to prevent
       committing the current user transaction when called in auto
       commit mode.

M      java/client/org/apache/derby/client/am/Statement.java

       Change the visibility of member isAutoCommittableStatement to
       package private.  No need to be public.

> Create framework for calling locator related stored procedures from client
> --------------------------------------------------------------------------
>                 Key: DERBY-2495
>                 URL: https://issues.apache.org/jira/browse/DERBY-2495
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Network Client
>            Reporter: Øystein Grøvlen
>         Assigned To: Øystein Grøvlen
>             Fix For:
>         Attachments: blobframework.diff, blobframework_v2.diff
> The client JDBC driver will need to call stored procedures (ref DERBY-2257) to operate
on LOBs identified by locators.  We should create a framework that implement the stored procedure
calls.  This way, the rest of the client code can call methods in this framework when needing
to call the stored procedures without having to prepare SQL statements themselves.  
> The framework should make sure that prepared statements are reused within a connection.
 Each procedure call should only be prepared once per connection.
> Since LOBs can not be parameters to stored procedures, the framework should make sure
that calls involving a byte[] or String that does not fit in a VARCHAR (FOR BIT DATA), are
split into several calls each operating on a fragment of the LOB.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message