db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2430) setObject(int targetType, Blob source) and setObject(int targetType, Clob source) should disallow updates on all targetTypes except BLOB and CLOB respectively
Date Fri, 09 Mar 2007 12:14:24 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479572
] 

V.Narayanan commented on DERBY-2430:
------------------------------------

I had one failure in derbynet/testSecMec.java when I ran derbyall and it did not seem related
to my patch.

I request for this patch to be please considered for a commit.

--------------------------------------------------------------------------------------------------
The diff for derbynet/testSecMec.java said this

< TEST_DS - USRSSBPWD + BUILTIN (T4):EXCEPTION testSecurityMechanism()  Connection authentication
failure occurred.  Reason: userid or password invalid.
< Turning OFF Derby BUILTIN authentication
< USRSSBPWD + BUILTIN (T5): jdbc:derby://xxxFILTERED_HOSTNAMExxx:xxxFILTEREDPORTxxx/wombat;user=neelima;password=lee;shutdown=true;securityMechanism=8
- EXCEPTION DERBY SQL error: SQLCODE: -1, SQLSTATE: 08006, SQLERRMC: Database 'wombat' shutdown.
< -----
< Testing with derby.drda.securityMechanism=INVALID_VALUE
< EXPECTED EXCEPTION DRDA_InvalidValue.U:Invalid value, INVALID_VALUE, for derby.drda.securityMechanism.
< -----
< Testing with derby.drda.securityMechanism=
< EXPECTED EXCEPTION DRDA_InvalidValue.U:Invalid value, , for derby.drda.securityMechanism.
< Completed testSecMec
Test Failed.

>  setObject(int targetType, Blob source) and setObject(int targetType, Clob source) should
disallow updates on all targetTypes except BLOB and CLOB respectively
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2430
>                 URL: https://issues.apache.org/jira/browse/DERBY-2430
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Network Client
>         Environment: All
>            Reporter: V.Narayanan
>         Assigned To: V.Narayanan
>         Attachments: setObjectForClobBlob_v1.diff, setObjectForClobBlob_v1.stat
>
>
> updateBlob(int columnIndex, Blob x), updateClob(int columnIndex, Clob x) can be implemented
by forwarding calls to  setObject(int targetType, Blob source), setObject(int targetType,
Clob source). If this this done then
> 1) updateClob on a CHAR/VARCHAR/LONG VARCHAR column throws an exception on the Embedded
Driver but not on the NetworkClient
> 2) updateBlob works on a CHAR/VARCHAR/LONG VARCHAR FOR BIT DATA throws an exception on
the Embedded Driver but not on the NetworkClient
> From what the JDBC 4.0 spec says (pg 198 table b-5) the Embedded behaviour seems to be
correct.
> This can be fixed by Matching Embedded behaviour. This would involve throwing an exception
in the cases mentioned above

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message