You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <de...@db.apache.org> on 2006/02/10 22:40:59 UTC

[jira] Created: (DERBY-945) Miscellaneous Connection methods added by JDBC 4

Miscellaneous Connection methods added by JDBC 4
------------------------------------------------

         Key: DERBY-945
         URL: http://issues.apache.org/jira/browse/DERBY-945
     Project: Derby
        Type: New Feature
  Components: JDBC  
    Reporter: Rick Hillegas
     Fix For: 10.2.0.0


As described in the JDBC spec section 3.1.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Assigned: (DERBY-945) Miscellaneous Connection methods added by JDBC 4

Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-945?page=all ]

Olav Sandstaa reassigned DERBY-945:
-----------------------------------

    Assign To: Olav Sandstaa

> Miscellaneous Connection methods added by JDBC 4
> ------------------------------------------------
>
>          Key: DERBY-945
>          URL: http://issues.apache.org/jira/browse/DERBY-945
>      Project: Derby
>         Type: New Feature
>   Components: JDBC
>     Reporter: Rick Hillegas
>     Assignee: Olav Sandstaa
>      Fix For: 10.2.0.0

>
> As described in the JDBC 4 spec section 3.1.
> This addresses new Connection methods added by JDBC 4 which are not addressed by the large object work (DERBY-796) and EOD work (DERBY-942). These additional methods are getClientInfo(), setClientInfo(), and isValid(). For the client info calls, we propose to not support the getting/setting of client info properties for release 10.2. Support for this functionality is optional. These properties are used for configuring session-scope, server-side diagnostics which Derby supplies through other mechanisms.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Closed: (DERBY-945) Miscellaneous Connection methods added by JDBC 4

Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-945?page=all ]
     
Rick Hillegas closed DERBY-945:
-------------------------------

    Resolution: Fixed

Sub-task closed.

> Miscellaneous Connection methods added by JDBC 4
> ------------------------------------------------
>
>          Key: DERBY-945
>          URL: http://issues.apache.org/jira/browse/DERBY-945
>      Project: Derby
>         Type: New Feature

>   Components: JDBC
>     Reporter: Rick Hillegas
>     Assignee: Olav Sandstaa
>      Fix For: 10.2.0.0

>
> As described in the JDBC 4 spec section 3.1.
> This addresses new Connection methods added by JDBC 4 which are not addressed by the large object work (DERBY-796) and EOD work (DERBY-942). These additional methods are getClientInfo(), setClientInfo(), and isValid(). For the client info calls, we propose to not support the getting/setting of client info properties for release 10.2. Support for this functionality is optional. These properties are used for configuring session-scope, server-side diagnostics which Derby supplies through other mechanisms.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (DERBY-945) Miscellaneous Connection methods added by JDBC 4

Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-945?page=all ]

Rick Hillegas updated DERBY-945:
--------------------------------

    Description: As described in the JDBC 4 spec section 3.1.  (was: As described in the JDBC spec section 3.1.)

> Miscellaneous Connection methods added by JDBC 4
> ------------------------------------------------
>
>          Key: DERBY-945
>          URL: http://issues.apache.org/jira/browse/DERBY-945
>      Project: Derby
>         Type: New Feature
>   Components: JDBC
>     Reporter: Rick Hillegas
>      Fix For: 10.2.0.0

>
> As described in the JDBC 4 spec section 3.1.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (DERBY-945) Miscellaneous Connection methods added by JDBC 4

Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-945?page=comments#action_12366228 ] 

Rick Hillegas commented on DERBY-945:
-------------------------------------

>From section 3.1 of the JDBC spec:

■ JDBC API changes
The following changes were made to existing JDBC interfaces.

■ Connection
Added the methods createBlob, createClob, createNClob,
createQueryObject, isValid, createXML, getClientInfo,
setClientInfo.

> Miscellaneous Connection methods added by JDBC 4
> ------------------------------------------------
>
>          Key: DERBY-945
>          URL: http://issues.apache.org/jira/browse/DERBY-945
>      Project: Derby
>         Type: New Feature
>   Components: JDBC
>     Reporter: Rick Hillegas
>      Fix For: 10.2.0.0

>
> As described in the JDBC 4 spec section 3.1.
> This addresses new Connection methods added by JDBC 4 which are not addressed by the large object work (DERBY-796) and EOD work (DERBY-942). These additional methods are getClientInfo(), setClientInfo(), and isValid(). For the client info calls, we propose to not support the getting/setting of client info properties for release 10.2. Support for this functionality is optional. These properties are used for configuring session-scope, server-side diagnostics which Derby supplies through other mechanisms.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (DERBY-945) Miscellaneous Connection methods added by JDBC 4

Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-945?page=all ]

Rick Hillegas updated DERBY-945:
--------------------------------

    Description: 
As described in the JDBC 4 spec section 3.1.

This addresses new Connection methods added by JDBC 4 which are not addressed by the large object work (DERBY-796) and EOD work (DERBY-942). These additional methods are getClientInfo(), setClientInfo(), and isValid(). For the client info calls, we propose to not support the getting/setting of client info properties for release 10.2. Support for this functionality is optional. These properties are used for configuring session-scope, server-side diagnostics which Derby supplies through other mechanisms.

  was:As described in the JDBC 4 spec section 3.1.


> Miscellaneous Connection methods added by JDBC 4
> ------------------------------------------------
>
>          Key: DERBY-945
>          URL: http://issues.apache.org/jira/browse/DERBY-945
>      Project: Derby
>         Type: New Feature
>   Components: JDBC
>     Reporter: Rick Hillegas
>      Fix For: 10.2.0.0

>
> As described in the JDBC 4 spec section 3.1.
> This addresses new Connection methods added by JDBC 4 which are not addressed by the large object work (DERBY-796) and EOD work (DERBY-942). These additional methods are getClientInfo(), setClientInfo(), and isValid(). For the client info calls, we propose to not support the getting/setting of client info properties for release 10.2. Support for this functionality is optional. These properties are used for configuring session-scope, server-side diagnostics which Derby supplies through other mechanisms.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira