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] Resolved: (DERBY-3690) EmbedPooledConnection doesn't reset schema when creating a new logical connection
Date Tue, 03 Jun 2008 12:46:45 GMT

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

Kristian Waagan resolved DERBY-3690.
------------------------------------

    Resolution: Fixed

Marking as fixed again.
A small excerpt of the latest patch (4-full_e) for DERBY-3327 was committed to the 10.4 branch
and it fixed the problem seen in the J2EEDataSourceTest.

Tinderbox test for 10.4 ran cleanly.
Fix can be verified and closed.

> EmbedPooledConnection doesn't reset schema when creating a new logical connection
> ---------------------------------------------------------------------------------
>
>                 Key: DERBY-3690
>                 URL: https://issues.apache.org/jira/browse/DERBY-3690
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.1.1.0, 10.2.1.6, 10.3.1.4, 10.4.1.3
>            Reporter: Knut Anders Hatlen
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.4.1.4, 10.5.0.0
>
>         Attachments: derby-3690-1a-reset_schema.diff, derby-3690-1b-reset_schema.diff,
PooledSchema.java
>
>
> If you set the schema on a logical connection obtained from EmbedPooledConnection, that
schema will also be the current schema for subsequent logical connections obtained from the
same EmbedPooledConnection.

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