[
https://issues.apache.org/jira/browse/DERBY-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan reassigned DERBY-3690:
--------------------------------------
Assignee: Kristian Waagan
I'll work this bug. I already have a fix for it as part of my patch for
DERBY-3596, and after some polishing and a regression test it should be good to
go.
I expect to get this done during the coming week.
> 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: 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.
