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 19:35:00 GMT
David Van Couvering wrote:

> I haven't heard any responses on this, so I am going to make the
> following changes/actions.  Speak now or... speak later, I guess :)
> - Use UUID to generate a unique id.  On the engine side I will use the
> UUID service; on the client side I will use BasicUUID hardcoded.

Sounds fine, but what still is the uniqueness of the string in just the
*simple* cases, never mind the multiple class loaders, multiple jvms etc?

- Connections returned from jdbc:default:connection?
  Unique string or string of parent connection?

- subsequent application connections returned from
PooledConnection.getConnection() - Unique I hope.


View raw message