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 "David Van Couvering (JIRA)" <de...@db.apache.org> on 2006/03/29 01:09:18 UTC

[jira] Created: (DERBY-1161) SQL State 42X89 should be SQL State 22005

SQL State 42X89 should be SQL State 22005
-----------------------------------------

         Key: DERBY-1161
         URL: http://issues.apache.org/jira/browse/DERBY-1161
     Project: Derby
        Type: Bug
  Components: Services  
    Reporter: David Van Couvering


The message for 42X89 is Types ''{0}'' and ''{1}'' are not type compatible. Neither type is assignable to the other type. The SQL spec has a standard SQL State 22005 which means "data exception - error in assignment".  It would appear this is exactly what is happening here.

NOTE: This bug can not be fixed in a minor release, as it would change an existing SQL State, which is a public, stable interface and can not change across minor releases.  The earliest this can be fixed is 11.0

-- 
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-1161) SQL State 42X89 should be SQL State 22005

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

David Van Couvering updated DERBY-1161:
---------------------------------------

    Priority: Minor  (was: Major)

> SQL State 42X89 should be SQL State 22005
> -----------------------------------------
>
>          Key: DERBY-1161
>          URL: http://issues.apache.org/jira/browse/DERBY-1161
>      Project: Derby
>         Type: Bug
>   Components: Services
>     Reporter: David Van Couvering
>     Priority: Minor

>
> The message for 42X89 is Types ''{0}'' and ''{1}'' are not type compatible. Neither type is assignable to the other type. The SQL spec has a standard SQL State 22005 which means "data exception - error in assignment".  It would appear this is exactly what is happening here.
> NOTE: This bug can not be fixed in a minor release, as it would change an existing SQL State, which is a public, stable interface and can not change across minor releases.  The earliest this can be fixed is 11.0

-- 
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-1161) SQL State 42X89 should be SQL State 22005

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

    Resolution: Invalid

Per Dan's comment, this is not a bug, it has to do with type incompatibility, not data incompatibility.

> SQL State 42X89 should be SQL State 22005
> -----------------------------------------
>
>          Key: DERBY-1161
>          URL: http://issues.apache.org/jira/browse/DERBY-1161
>      Project: Derby
>         Type: Bug
>   Components: Services
>     Reporter: David Van Couvering
>     Priority: Minor

>
> The message for 42X89 is Types ''{0}'' and ''{1}'' are not type compatible. Neither type is assignable to the other type. The SQL spec has a standard SQL State 22005 which means "data exception - error in assignment".  It would appear this is exactly what is happening here.
> NOTE: This bug can not be fixed in a minor release, as it would change an existing SQL State, which is a public, stable interface and can not change across minor releases.  The earliest this can be fixed is 11.0

-- 
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-1161) SQL State 42X89 should be SQL State 22005

Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-1161?page=comments#action_12372162 ] 

Daniel John Debrunner commented on DERBY-1161:
----------------------------------------------

In this specific case '22' is a data exception, some exception raised
due to the value of the data. '42' is a compile time error, in this case
raised because the types are not assignable to each other, not because
the specific data values are not assignable to each other.

I'm not sure this bug is valid.

> SQL State 42X89 should be SQL State 22005
> -----------------------------------------
>
>          Key: DERBY-1161
>          URL: http://issues.apache.org/jira/browse/DERBY-1161
>      Project: Derby
>         Type: Bug
>   Components: Services
>     Reporter: David Van Couvering
>     Priority: Minor

>
> The message for 42X89 is Types ''{0}'' and ''{1}'' are not type compatible. Neither type is assignable to the other type. The SQL spec has a standard SQL State 22005 which means "data exception - error in assignment".  It would appear this is exactly what is happening here.
> NOTE: This bug can not be fixed in a minor release, as it would change an existing SQL State, which is a public, stable interface and can not change across minor releases.  The earliest this can be fixed is 11.0

-- 
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-1161) SQL State 42X89 should be SQL State 22005

Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-1161?page=comments#action_12372164 ] 

Daniel John Debrunner commented on DERBY-1161:
----------------------------------------------

Also comment on the NOTE about it not being fixed until 11.0.

Derby has not defined any policy on such an issue so it's premature to be putting such "rules" in place.

> SQL State 42X89 should be SQL State 22005
> -----------------------------------------
>
>          Key: DERBY-1161
>          URL: http://issues.apache.org/jira/browse/DERBY-1161
>      Project: Derby
>         Type: Bug
>   Components: Services
>     Reporter: David Van Couvering
>     Priority: Minor

>
> The message for 42X89 is Types ''{0}'' and ''{1}'' are not type compatible. Neither type is assignable to the other type. The SQL spec has a standard SQL State 22005 which means "data exception - error in assignment".  It would appear this is exactly what is happening here.
> NOTE: This bug can not be fixed in a minor release, as it would change an existing SQL State, which is a public, stable interface and can not change across minor releases.  The earliest this can be fixed is 11.0

-- 
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