db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Van Couvering <da...@vancouvering.com>
Subject Re: [jira] Updated: (DERBY-243) connection toString should uniquely identify the connection
Date Wed, 25 May 2005 23:11:45 GMT
Hi, Kathey.  It's not a huge pressure to get this done (at least on my 
end), but I agree it would be great if somebody else did the initial 
verification that it works OK.

Yes, the Error Log VTI output should have changed.  I will run a test to 
make sure it looks OK.

David

Kathey Marsden wrote:

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

Mime
View raw message