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 "Tomohito Nakayama (JIRA)" <de...@db.apache.org> on 2006/10/08 06:11:20 UTC
[jira] Created: (DERBY-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
------------------------------------------------------------------------------------
Key: DERBY-1942
URL: http://issues.apache.org/jira/browse/DERBY-1942
Project: Derby
Issue Type: Bug
Components: JDBC
Reporter: Tomohito Nakayama
The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
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-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1942?page=comments#action_12441151 ]
Tomohito Nakayama commented on DERBY-1942:
------------------------------------------
Reading the spcec, java.sql.Time is not compatible to JDBC TIMESTAMP.
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: http://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assigned To: Tomohito Nakayama
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
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-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1942?page=all ]
Tomohito Nakayama updated DERBY-1942:
-------------------------------------
Derby Info: [Existing Application Impact, Release Note Needed] (was: [Release Note Needed])
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: http://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assigned To: Tomohito Nakayama
> Attachments: DERBY-1942.patch
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
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-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1942?page=all ]
Tomohito Nakayama reassigned DERBY-1942:
----------------------------------------
Assignee: Tomohito Nakayama
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: http://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assigned To: Tomohito Nakayama
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
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-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomohito Nakayama updated DERBY-1942:
-------------------------------------
Attachment: releaseNote.html
I wrote.
Please review it ...
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: https://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assignee: Tomohito Nakayama
> Attachments: DERBY-1942.patch, releaseNote.html
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1942?page=comments#action_12442640 ]
Dag H. Wanvik commented on DERBY-1942:
--------------------------------------
Should this issue perhaps have the "existing application impact" and
release note needed" flags set? It seems you have made something
illegal that worked before...
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: http://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assigned To: Tomohito Nakayama
> Attachments: DERBY-1942.patch
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
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-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomohito Nakayama updated DERBY-1942:
-------------------------------------
Attachment: releaseNote.html
I updated release note.
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: https://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assignee: Tomohito Nakayama
> Fix For: 10.3.0.0
>
> Attachments: DERBY-1942.patch, releaseNote.html, releaseNote.html, releaseNote_reviewed.html
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502306 ]
Tomohito Nakayama commented on DERBY-1942:
------------------------------------------
Thank you for brushing up the note :)
I think contents of Application Changes Required section was changed a little bit.
I read the description that TIME data type is completely impossible to use.
In the truth, application is not prohibitted from using TIME data type if it was appropriate.
I'm thinking to modify as next :
It is needed to correct inappropriate use of TIME data type to use the TIMESTAMP data type insteadly.
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: https://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assignee: Tomohito Nakayama
> Fix For: 10.3.0.0
>
> Attachments: DERBY-1942.patch, releaseNote.html, releaseNote_reviewed.html
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502986 ]
Tomohito Nakayama commented on DERBY-1942:
------------------------------------------
Application still can use TIME data type in some situation ...
The situation application can still use TIME data type is the case information of date is not needed ....
How about this ?
Applications using the TIME data type must use the TIMESTAMP data type instead,
if date information is needed besides time information.
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: https://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assignee: Tomohito Nakayama
> Fix For: 10.3.0.0
>
> Attachments: DERBY-1942.patch, releaseNote.html, releaseNote_reviewed.html
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Laura Stewart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laura Stewart updated DERBY-1942:
---------------------------------
Attachment: releaseNote_reviewed.html
I reviewed and edited the content of the release note document.
Please check that I did not change the technical meaning of this change.
You will also need to rename the file.
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: https://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assignee: Tomohito Nakayama
> Fix For: 10.3.0.0
>
> Attachments: DERBY-1942.patch, releaseNote.html, releaseNote_reviewed.html
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1942?page=comments#action_12442396 ]
Tomohito Nakayama commented on DERBY-1942:
------------------------------------------
Committed.
Sending java/engine/org/apache/derby/iapi/types/SQLTimestamp.java
Sending java/testing/org/apache/derbyTesting/functionTests/master/jdk14/updatableResultSet.out
Sending java/testing/org/apache/derbyTesting/functionTests/master/parameterMapping.out
Sending java/testing/org/apache/derbyTesting/functionTests/master/updatableResultSet.out
Sending java/testing/org/apache/derbyTesting/functionTests/tests/lang/timestampArith.java
Sending java/testing/org/apache/derbyTesting/functionTests/tests/lang/updatableResultSet.java
Transmitting file data ......
Committed revision 464202.
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: http://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assigned To: Tomohito Nakayama
> Attachments: DERBY-1942.patch
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
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-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501516 ]
Tomohito Nakayama commented on DERBY-1942:
------------------------------------------
I have started to write release note.
Please wait for a moment ...
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: https://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assignee: Tomohito Nakayama
> Attachments: DERBY-1942.patch
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Laura Stewart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502895 ]
Laura Stewart commented on DERBY-1942:
--------------------------------------
How about this:
Application Changes Required
Applications that call the setTime method using the TIME data type should use the TIMESTAMP data type instead.
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: https://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assignee: Tomohito Nakayama
> Fix For: 10.3.0.0
>
> Attachments: DERBY-1942.patch, releaseNote.html, releaseNote_reviewed.html
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1942?page=comments#action_12441434 ]
Tomohito Nakayama commented on DERBY-1942:
------------------------------------------
This modification would affect DATETIMEDIFF scalar function.
Now DATETIMEDIFF function accept java.sql.TIME as type compatible for parameters.
However modification in this patch would take it as error.
I think new behavior would proper behavior but a little strict....
In the JDBC spec, signature for TIMESTAMPDIFF function was described as next.
TIMESTAMPDIFF(interval, An integer representing the number of interval
timestamp1, timestamp2)
I think this description is implicit definition that the parameter should be timestamp.
Well ... I will take strict way, means to regard java.sql.TIME as incompatible type for parameters in DATETIMEDIFF function.
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: http://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assigned To: Tomohito Nakayama
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
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-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-1942:
---------------------------------
Attachment: releaseNote.html
Scrubbing the release note so that it survives the SAX parser in the release note generator. Removed some cruft inserted by an html editor.
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: https://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assignee: Tomohito Nakayama
> Fix For: 10.3.0.0
>
> Attachments: DERBY-1942.patch, releaseNote.html, releaseNote.html, releaseNote.html, releaseNote_reviewed.html
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1942?page=all ]
Tomohito Nakayama updated DERBY-1942:
-------------------------------------
Attachment: DERBY-1942.patch
* Description of the patch
* Make it impossible to assign TIME type value to TIMESTAMP variable
in order to unify the behavior of setNull(Types.TIME) and setTime(null).
* Result of the test
* Executed derbyall and found only intermittent error in derbynet/testSecMec.java.
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: http://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assigned To: Tomohito Nakayama
> Attachments: DERBY-1942.patch
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
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-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomohito Nakayama updated DERBY-1942:
-------------------------------------
Derby Info: [Existing Application Impact, Release Note Needed] (was: [Release Note Needed, Existing Application Impact])
Fix Version/s: 10.3.0.0
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: https://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assignee: Tomohito Nakayama
> Fix For: 10.3.0.0
>
> Attachments: DERBY-1942.patch, releaseNote.html
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1942?page=all ]
Tomohito Nakayama resolved DERBY-1942.
--------------------------------------
Resolution: Fixed
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: http://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assigned To: Tomohito Nakayama
> Attachments: DERBY-1942.patch
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
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-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-1942:
---------------------------------
Attachment: releaseNote.html
Attaching new version of the release note. This replaces the uppercase paragraph tags with lowercase paragraph tags so that the case-sensitive SAX machinery can find the summary line for this note.
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: https://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assignee: Tomohito Nakayama
> Fix For: 10.3.0.0
>
> Attachments: DERBY-1942.patch, releaseNote.html, releaseNote.html, releaseNote.html, releaseNote.html, releaseNote_reviewed.html
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505561 ]
Tomohito Nakayama commented on DERBY-1942:
------------------------------------------
Thank you for your work, Rick !
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: https://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assignee: Tomohito Nakayama
> Fix For: 10.3.0.0
>
> Attachments: DERBY-1942.patch, releaseNote.html, releaseNote.html, releaseNote.html, releaseNote.html, releaseNote_reviewed.html
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501271 ]
Kathey Marsden commented on DERBY-1942:
---------------------------------------
Tomohito said:
>* Description of the patch
> * Make it impossible to assign TIME type value to TIMESTAMP variable
> in order to unify the behavior of setNull(Types.TIME) and setTime(null).
I am concerned about compatibility with regard to this patch as it was hit by several tests. I think it is likely to affect applications and am not sure that the benefit is worth that risk. At the very least we need a comprehensive release note.
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: https://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assignee: Tomohito Nakayama
> Attachments: DERBY-1942.patch
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
Posted by "Tomohito Nakayama (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1942?page=all ]
Tomohito Nakayama updated DERBY-1942:
-------------------------------------
Derby Info: [Release Note Needed]
> There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1942
> URL: http://issues.apache.org/jira/browse/DERBY-1942
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Tomohito Nakayama
> Assigned To: Tomohito Nakayama
> Attachments: DERBY-1942.patch
>
>
> The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error.
> However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error .
> see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554
--
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