db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3328) Extend client JDBC object factory with methods to create objects required for statement pooling
Date Sat, 23 Feb 2008 18:43:24 GMT

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

Kristian Waagan updated DERBY-3328:
-----------------------------------

    Attachment: derby-3328-2a-change_signatures.stat
                derby-3328-2a-change_signatures.diff

'derby-3328-2a-change_signatures.diff' is preparation patch for some other changes down the
line.
It changes the signatures of the factory methods for logical statements, and implements the
required changes in the affected classes.
The change is implemented to be able to support other "features", first of all DERBY-3457
which handles closing of logical statements when a logical connection is closed.

Due to limited time, I will commit this very quickly, but it is of course (and as usual) opportunity
to comment on the changes after they have gone in.

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


Mime
View raw message