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-3690) EmbedPooledConnection doesn't reset schema when creating a new logical connection
Date Tue, 27 May 2008 06:51:58 GMT

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

Kristian Waagan updated DERBY-3690:
-----------------------------------

    Attachment: derby-3690-1b-reset_schema.diff

'derby-3690-1b-reset_schema.diff' is identical to 1a, except for three additions to comments
to link to this Jira issue.
Regression tests have been run without failures (Sun JDK 1.6.0, Solaris 10).

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