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 "V.Narayanan (JIRA)" <ji...@apache.org> on 2007/03/09 08:51:24 UTC
[jira] Created: (DERBY-2430) setObject(int targetType, Blob
source) and setObject(int targetType, Clob source) should disallow updates
on all targetTypes except BLOB and CLOB respectively
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
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.
[jira] Closed: (DERBY-2430) setObject(int targetType, Blob source)
and setObject(int targetType, Clob source) should disallow updates on all
targetTypes except BLOB and CLOB respectively
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
V.Narayanan closed DERBY-2430.
------------------------------
> 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
> Assignee: V.Narayanan
> Fix For: 10.3.0.0
>
> Attachments: releaseNote.html, 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.
[jira] Reopened: (DERBY-2430) setObject(int targetType, Blob
source) and setObject(int targetType, Clob source) should disallow updates
on all targetTypes except BLOB and CLOB respectively
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas reopened DERBY-2430:
----------------------------------
Reopen issue so that I can scrub the release note.
> 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
> Assignee: V.Narayanan
> Fix For: 10.3.0.0
>
> Attachments: releaseNote.html, 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.
[jira] Resolved: (DERBY-2430) setObject(int targetType, Blob
source) and setObject(int targetType, Clob source) should disallow updates
on all targetTypes except BLOB and CLOB respectively
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
V.Narayanan resolved DERBY-2430.
--------------------------------
Resolution: Fixed
All patches submitted and committed and release note added
> 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
> Assignee: V.Narayanan
> Fix For: 10.3.0.0
>
> Attachments: releaseNote.html, 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.
[jira] Updated: (DERBY-2430) setObject(int targetType, Blob
source) and setObject(int targetType, Clob source) should disallow updates
on all targetTypes except BLOB and CLOB respectively
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
V.Narayanan updated DERBY-2430:
-------------------------------
Derby Info: [Patch Available]
> 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.
[jira] Updated: (DERBY-2430) setObject(int targetType, Blob
source) and setObject(int targetType, Clob source) should disallow updates
on all targetTypes except BLOB and CLOB respectively
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2430:
---------------------------------
Attachment: releaseNote.html
Attaching scrubbed version the release note. This removes the cruft inserted by an html editor, which the SAX parser can't digest.
> 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
> Assignee: V.Narayanan
> Fix For: 10.3.0.0
>
> Attachments: releaseNote.html, releaseNote.html, 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.
[jira] Updated: (DERBY-2430) setObject(int targetType, Blob
source) and setObject(int targetType, Clob source) should disallow updates
on all targetTypes except BLOB and CLOB respectively
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
V.Narayanan updated DERBY-2430:
-------------------------------
Attachment: setObjectForClobBlob_v1.stat
setObjectForClobBlob_v1.diff
The above patch removes the code that allows types other than Clob and Blob in the setObject method of CrossConverters class. I have also fixed a failure in UpdatableResultSetTest.java . This involved adding the SQLState of the exception that will be thrown when we do a updateClob or a updateBlob on the disallowed types into the updateObjectRulesTableForNetworkClient array.
I am running derbyall with this patch. I shall post the results soon. I have put this up for review.
Narayanan
> 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.
[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
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480103 ]
V.Narayanan commented on DERBY-2430:
------------------------------------
pardon my earlier typo. I meant to say I did a "svn status" after doing a "svn update".
> 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.
[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
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480102 ]
V.Narayanan commented on DERBY-2430:
------------------------------------
I did a svn update in the checkout in which I had done this modification. After this I did a svn update and the output did not reveal any broken files
M java/testing/org/apache/derbyTesting/functionTests/tests/lang/UpdatableResultSetTest.java
M java/client/org/apache/derby/client/am/CrossConverters.java
X tools/testing/derby
This issue blocks 2443 for which I have put in a patch for review alone
I request a interested person to consider this patch for review and comment and if everything is ok a commit recommendation or a commit.
thanx,
Narayanan
> 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.
[jira] Updated: (DERBY-2430) setObject(int targetType, Blob
source) and setObject(int targetType, Clob source) should disallow updates
on all targetTypes except BLOB and CLOB respectively
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-2430:
---------------------------------
Attachment: releaseNote.html
Correct unbalanced paragraph tag in release note.
> 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
> Assignee: V.Narayanan
> Fix For: 10.3.0.0
>
> Attachments: releaseNote.html, releaseNote.html, releaseNote.html, 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.
[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
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480307 ]
V.Narayanan commented on DERBY-2430:
------------------------------------
Thank you for the commit knut. This patch blocks issue 2443 and this commit will help me in submitting a final patch to that issue.
Thanx a ton for this one,
Narayanan
> 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
> Fix For: 10.3.0.0
>
> 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.
[jira] Resolved: (DERBY-2430) setObject(int targetType, Blob
source) and setObject(int targetType, Clob source) should disallow updates
on all targetTypes except BLOB and CLOB respectively
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen resolved DERBY-2430.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Derby Info: [Release Note Needed] (was: [Patch Available])
Thanks Narayanan. The patch looks good. Committed revision 517577.
I set the "Release Note Needed" flag to indicate that this change should be mentioned in the release notes for 10.3. It would be OK to incorporate the release note for this issue into the release note for DERBY-1610.
> 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
> Fix For: 10.3.0.0
>
> 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.
[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
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (DERBY-2430) setObject(int targetType, Blob source)
and setObject(int targetType, Clob source) should disallow updates on all
targetTypes except BLOB and CLOB respectively
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
V.Narayanan closed DERBY-2430.
------------------------------
> 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
> Assignee: V.Narayanan
> Fix For: 10.3.0.0
>
> 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.
[jira] Assigned: (DERBY-2430) setObject(int targetType, Blob
source) and setObject(int targetType, Clob source) should disallow updates
on all targetTypes except BLOB and CLOB respectively
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
V.Narayanan reassigned DERBY-2430:
----------------------------------
Assignee: V.Narayanan
> 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
>
> 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.
[jira] Closed: (DERBY-2430) setObject(int targetType, Blob source)
and setObject(int targetType, Clob source) should disallow updates on all
targetTypes except BLOB and CLOB respectively
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas closed DERBY-2430.
--------------------------------
Resolution: Fixed
> 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
> Assignee: V.Narayanan
> Fix For: 10.3.0.0
>
> Attachments: releaseNote.html, releaseNote.html, releaseNote.html, 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.
[jira] Reopened: (DERBY-2430) setObject(int targetType, Blob
source) and setObject(int targetType, Clob source) should disallow updates
on all targetTypes except BLOB and CLOB respectively
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
V.Narayanan reopened DERBY-2430:
--------------------------------
Re-opening to attach release note.
> 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
> Assignee: V.Narayanan
> Fix For: 10.3.0.0
>
> Attachments: releaseNote.html, 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.
[jira] Updated: (DERBY-2430) setObject(int targetType, Blob
source) and setObject(int targetType, Clob source) should disallow updates
on all targetTypes except BLOB and CLOB respectively
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
V.Narayanan updated DERBY-2430:
-------------------------------
Attachment: releaseNote.html
Attaching the release note for this issue
> 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
> Assignee: V.Narayanan
> Fix For: 10.3.0.0
>
> Attachments: releaseNote.html, 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.