Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <429502CE.5080201@sbcglobal.net>
Date: Wed, 25 May 2005 15:57:18 -0700
From: Kathey Marsden <kmarsdenderby@sbcglobal.net>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: [jira] Updated: (DERBY-243) connection toString should uniquely
 identify the connection
References: <393327434.1117056069476.JavaMail.jira@ajax.apache.org>
In-Reply-To: <393327434.1117056069476.JavaMail.jira@ajax.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

David Van Couvering (JIRA) wrote:

>Here is an updated patch for this item.  This addresses my previous comment by pushing
>the unique id down to the LanguageConnectionContext.
>  
>
Thanks David,

It is probably going to be this weekend before I have a chance to look
at this patch.  Do you think you can lobby someone else  (maybe some of
our friends from Norway) to do the initial review and try out this
patch?  It would be a huge help in moving this along.  Also I wanted to
mention that I thought I remember you mentioning that you were changing
a value that already shows up in the  Error Log VTI from an integer to
the UUID.  If that's the case, I think that means the VTI will have to
be changed.    If what prints in the VTI's was affected at all, could 
give it a try and make sure it still works ok?  I don't see the test
that I think used to be there to test the diagnostic VTI's.   Sorry I
can't review right away. Got myself in a bit  of a bind this week #:(

Kathey