Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 73012 invoked from network); 28 May 2008 06:20:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 May 2008 06:20:06 -0000 Received: (qmail 26516 invoked by uid 500); 28 May 2008 06:20:07 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 26476 invoked by uid 500); 28 May 2008 06:20:07 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 26465 invoked by uid 99); 28 May 2008 06:20:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 May 2008 23:20:07 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 May 2008 06:19:28 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 0D343234C126 for ; Tue, 27 May 2008 23:19:45 -0700 (PDT) Message-ID: <2100785888.1211955585032.JavaMail.jira@brutus> Date: Tue, 27 May 2008 23:19:45 -0700 (PDT) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Reopened: (DERBY-3690) EmbedPooledConnection doesn't reset schema when creating a new logical connection In-Reply-To: <645265898.1211541475947.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan reopened DERBY-3690: ------------------------------------ Looking at my test logs, I see that I accidentally ran the regression tests 4 times against trunk... Two of those were meant for the 10.4 branch. I'm reopening to look at DERBY-3692. I have already verified that this checkin (r660408) caused the errors, but I do not know why yet. Depending on the investigation, I will either fix this for 10.4 or back out the original fix. > 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.