db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: [jira] Updated: (DERBY-243) connection toString should uniquely identify the connection
Date Wed, 11 May 2005 22:44:52 GMT
David Van Couvering wrote:

> That said, if I understand things correctly, the BrokeredConnection is
> mostly a proxy to catch things like Connection.close(), and that the
> right thing to do in this case is return the toString() of the
> underlying EmbedConnection.   We should always delegate to the actual
> physical database connection, just like BrokeredConnection does for
> everything else.

Yes, though I would add a little more weight behind what
BrokeredConnection is for. It's main role is to provide a unique logical
connection object for the application.

In Derby both the logical connection and the physical connection are
represented by Connection objects, which can confuse the issue.

Dan.



Mime
View raw message