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 Thu, 12 May 2005 23:34:18 GMT
David Van Couvering wrote:
[snip]

>
> Well, I like this, except that for application code, which is where
> the majority of debugging would take place when using Derby, it would
> *always* say "Physical Connection".


Actually I just thought of it as more of a documentation feature
describing our new toString() behaviour, since the connection semantics
are subtle.   I thought, for instance, it might make it clearer for the
stored procedure (jdbc:default:connection)  case,  that we are reporting
the id for the parent connection and not a separate connection id.

Anyway, I better just wait for the patch and  really understand the new
toString() before I start worrying about descriptive names. 
"Connection" is ok with me for now.

Kathey



Mime
View raw message