db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: [jira] Updated: (DERBY-243) connection toString should uniquely identify the connection
Date Tue, 17 May 2005 17:22:26 GMT
David Van Couvering (JIRA) wrote:

>I have replaced the old patch with this one.  This one uses UUID to identify a connection
>It also provides independent connection strings for PooledConnection classes.  
Hi David

Just so I understand the connection id semantics as I review this patch,
could you tell me whether the following statements are true or false
with regard to your patch. Please specify if the behaviour is different
for embedded and client.

1)  Each physical connection has its own unique connection id,
regardless of how it is obtained by the application.

2) If a stored procedure is called from a connection with connection id
X,  and the stored procedure obtains a connection with
DriverManager.getConnection("jdbc:default:connection"),  the connection
in the stored procedure will also have
    connection id X.

3) Every logical connection obtained from a single pooled connection
will  have the same connection id.



View raw message