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-478) Function to force closing connection (and session)
Date Thu, 28 Jul 2005 17:22:04 GMT
Rick Hillegas wrote:
> Hi David,
> 
> Where in the JDBC 4 spec would this be? I seem to have missed it.
> There's a fairly long  section on Connection Pooling, but I didn't see
> this issue addressed.

I'm not sure it should be. Applications should not have the ability to
close the underlying physical connection from their logical connection
object. An api exists to close the physical connection, the close method
on PooledConnection. But applications do not (and should not) have
access to PooledConnection.

Dan.




> 
> Thanks,
> -Rick
> 
> David Van Couvering wrote:
> 
>> Isn't this part of the proposed interfaces for the JDBC 4 spec?
>>
>> Tomohito Nakayama (JIRA) wrote:
>>
>>>     [ http://issues.apache.org/jira/browse/DERBY-478?page=all ]
>>>
>>> Tomohito Nakayama updated DERBY-478:
>>> ------------------------------------
>>>
>>>        Summary: Function to force closing connection (and session) 
>>> (was: Force to close connection and session)
>>>    Description: When connection exists in ConnectionPool , there are
>>> no way to ensure closing connection inside the ConnectionPool from
>>> application program just using jdbc interface.
>>>
>>> I think there exists needs to force closing connection when it is
>>> needed to ensure closing of connection.  was:When connection exists
>>> in ConnectionPool , there are no way to ensure
>>>
>>>  
>>>
>>>> Function to force closing connection (and session)
>>>> --------------------------------------------------
>>>>
>>>>         Key: DERBY-478
>>>>         URL: http://issues.apache.org/jira/browse/DERBY-478
>>>>     Project: Derby
>>>>        Type: Improvement
>>>>  Components: Network Server
>>>>    Reporter: Tomohito Nakayama
>>>>   
>>>
>>>
>>>
>>>  
>>>
>>>> When connection exists in ConnectionPool , there are no way to
>>>> ensure closing connection inside the ConnectionPool from application
>>>> program just using jdbc interface.
>>>> I think there exists needs to force closing connection when it is
>>>> needed to ensure closing of connection.    
>>>
>>>
>>>
>>>  
>>>
> 
> 
> 



Mime
View raw message