Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <315137519.1204291491250.JavaMail.jira@brutus>
Date: Fri, 29 Feb 2008 05:24:51 -0800 (PST)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Closed: (DERBY-3328) Extend client JDBC object factory with
 methods to create objects required for statement pooling
In-Reply-To: <15907683.1200590374167.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kristian Waagan closed DERBY-3328.
----------------------------------


I don't see anything more coming up for this issue.

> Extend client JDBC object factory with methods to create objects required for statement pooling
> -----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3328
>                 URL: https://issues.apache.org/jira/browse/DERBY-3328
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Network Client
>    Affects Versions: 10.4.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.4.0.0
>
>         Attachments: derby-3328-1a-extend_jdbc_objectfactories.diff, derby-3328-1a-extend_jdbc_objectfactories.stat, derby-3328-2a-change_signatures.diff, derby-3328-2a-change_signatures.stat
>
>
> Since statement pooling introduces new types of objects, the factories must be extended to handle these new types.
> This step is primarily required because we support multiple versions of the JDBC standard, which in turn implies running with different interfaces and JVM versions with differing features.

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