[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

["Kristian Waagan (JIRA)" <ji...@apache.org>]

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

Kristian Waagan updated DERBY-3326:
-----------------------------------

    Attachment: derby-3326-9a-temp_table_test.diff

'derby-3326-9a-temp_table_test.diff' adds a test in jdbcapi.StatementPoolingTest that tests that temporary tables are deleted and not visible across logical connections.
Also set the createDatabase to create on the data source for some of the tests, so they can be run individually and not fail if the database hasn't been created yet.

Committed to trunk with revision 644360 and to the 10.4 branch with revision 644373.

> Introduce a caching logical connection and logical prepared statement in the client driver
> ------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3326
>                 URL: https://issues.apache.org/jira/browse/DERBY-3326
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JDBC, Network Client
>    Affects Versions: 10.4.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>             Fix For: 10.4.0.0
>
>         Attachments: derby-3326-1a_cpds_testing_preparation.diff, derby-3326-1a_cpds_testing_preparation.stat, derby-3326-1b_cpds_testing_preparation.diff, derby-3326-2a-method_rename.diff, derby-3326-3a-new_classes.diff, derby-3326-3a-new_classes.stat, derby-3326-3b-new_classes.diff, derby-3326-3b-new_classes.stat, derby-3326-3c-new_classes.diff, derby-3326-4a-cpdsc_shutEngine.diff, derby-3326-5a-enable_logicalstmtentity_pptest.diff, derby-3326-6a-npe_fix_synch_CLC.diff, derby-3326-6b-npe_fix_synch_CLC.diff, derby-3326-7a-prepare_column_indexes_names_fix.diff, derby-3326-8a-use_session_data_caching.diff, derby-3326-9a-temp_table_test.diff
>
>
> A logical connection with statement caching capabilities is required to support JDBC prepared statement pooling. Further, a logical prepared statement object is also needed.
> The logical prepared statements will be generated by the logical connection's 'prepareStatement'-method.

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