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 "Deepa Remesh (JIRA)" <de...@db.apache.org> on 2005/07/07 23:33:17 UTC
[jira] Created: (DERBY-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
-------------------------------------------------------------------------------------
Key: DERBY-447
URL: http://issues.apache.org/jira/browse/DERBY-447
Project: Derby
Type: Bug
Components: JDBC
Reporter: Deepa Remesh
Assigned to: Deepa Remesh
The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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
Re: [jira] Created: (DERBY-447) getBoolean() throws data conversion
exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Hi Lance,
>>>>> "LJA" == Lance J Andersen <La...@Sun.COM> wrote:
LJA>
LJA> The DatabaseMetaData method supportsConvert is used to validate what the
LJA> scalar escape function CONVERT can be used for based on the
LJA> driver/database combo.
LJA>
LJA> The javadoc for the supportsConvert(arg1, arg2) should clarified
LJA> a bit more.
Agreed.
LJA>
LJA> As far as the name of the SQLTYPE for the Convert scalar function,
LJA> drivers were doing this in an inconsistant manner. adding the SQL_
LJA> prefix brings it in line with ODBC. Drivers that do not support the
LJA> SQL_ prefix (some drivers support with and without the prefix), will be
LJA> required to support the prefix and to continue to optional support
LJA> without the prefix.
LJA>
LJA> Is there an additional question here that i might have missed?
Yes, sorry I wasn't clear enough. The question concerns the description
in section 15.2.3.1 in the JDBC 4.0 spec, which describes the
conversions performed by the ResultSet "getter" methods. These
conversions are described in appendix B-2, but the spec also states:
"The method DataBaseMetaData.supportsConvert(int fromType, int toType)
returns true if the driver supports the given conversion."
The point is, this conversion (the "getter conversion") is another
(kind of) conversion than that performed by the CONVERT scalar
function, and thus the reference to supportsConvert in 15.2.3.1 above
is not correct?
The signature from "getter" methods is essentially "from: SQLtype to:
Java type", whereas the signature for CONVERT is "from: SQLtype, to:
SQLtype", right?
Perhaps there should have been additional DatabaseMataData methods to
allow querying what kind of conversions are supported for "getters"
(from SQLtype to Java types) (and vice versa for setters)?
Dag
LJA>
LJA> -lance
LJA>
LJA> Dag H. Wanvik wrote:
LJA>
LJA> >Hi,
LJA> >
LJA> >(Lance, see question to you below)
LJA> >
LJA> >
LJA> >
LJA> >>>>>>"DJD" == Daniel John Debrunner <dj...@debrunners.com> wrote:
LJA> >>>>>>
LJA> >>>>>>
LJA> >DJD>
LJA> >DJD> Dag H. Wanvik wrote:
LJA> >DJD> > DJD> There's some inconsistency here, the ResultSet getter methods are
LJA> >DJD> > DJD> converting from SQL data types to Java data types. This supportsConvert
LJA> >DJD> > DJD> method takes two arguments, both of which describe SQL data types.
LJA> >DJD> >
LJA> >DJD> > Yes, you are right. Something for Lance to clarify :)
LJA> >DJD> > But it would seem the no-args supportsConvert() should return false
LJA> >DJD> > until we add support for CONVERT.
LJA> >DJD>
LJA> >DJD> And just to be clear, this is the JDBC CONVERT function from section C.5
LJA> >DJD> of JDBC 3.0, correct?
LJA> >
LJA> >Yes.
LJA> >
LJA> >DJD>
LJA> >DJD> I think there is some issue with CONVERT in JDBC 4.0, where the format
LJA> >DJD> of the second argument is changing, from INTEGER to SQL_INTEGER or
LJA> >DJD> something like that?
LJA> >
LJA> >Hmm.. I did a short check.. The DataBaseMetaData.supportsConvert has
LJA> >int (from java.sql.Types aka JDBC types/SQLtypes) for both arguments
LJA> >(both in JDBC 3.0 and early draft 4.0), which makes sense since the
LJA> >API speaks of describing the support/behavior of CONVERT, and this
LJA> >conversion all happens in the SQL domain.
LJA> >
LJA> >[On a side note: actually the Javadoc for supportsConvert speaks of
LJA> >(unqualified) CONVERT, without being explicit on this being the C.5
LJA> >escape JDBC CONVERT, not the SQL character set CONVERT, but I guess
LJA> >that's kind of obvious..?]
LJA> >
LJA> >Also, in both the JDBC 3.0 and 4.0 spec, the escape function CONVERT
LJA> >has SQLtype as the second argument, "value" being given as the first.
LJA> >
LJA> >The PreparedStatement "setter"/ ResultSet "getter" functions mappings,
LJA> >though, convert from and to Java types, given by the tables in the B
LJA> >appendix.
LJA> >
LJA> >I think the problem is that section 15.2.3.1 in the JDBC 4.0 spec
LJA> >(14.2.3.1 in 3.0) erroneously states that
LJA> >DataBaseMetaData.supportsConvert says ANYTHING about the mapping for
LJA> >getter methods. Interestingly, the corresponding section on conversion
LJA> >for *setter* methods makes no mention of
LJA> >DataBaseMetaData.supportsConvert (section 13.2.2.1 in 4.0 as well as
LJA> >in 3.0). Nor do the IN, OUT, INOUT descriptions.
LJA> >
LJA> >
LJA> >
LJA> >>15.2.3.1 Data Type Conversions
LJA> >>The recommended ResultSet getter method for each JDBC type is shown
LJA> >>in TABLE B-6 on page B-210. This table also shows all of the
LJA> >>possible conversions that a JDBC driver may support. The method
LJA> >>DataBaseMetaData.supportsConvert(int fromType, int toType) returns
LJA> >>
LJA> >>
LJA> >************************************
LJA> >
LJA> >
LJA> >>true if the driver supports the given conversion.
LJA> >>
LJA> >>
LJA> >
LJA> >Lance, do you agree this is wrong? If it is correct, please explain
LJA> >what I am missing here..!
LJA> >
LJA> >Notwhithstanding this, the Derby implementation of no-args
LJA> >DataBaseMetaData.supportsConvert() returns true, indicating we support
LJA> >C.5 CONVERT, which we do not AFAICS, and I suggest we make a JIRA for
LJA> >that.
LJA> >
LJA> >Dag
LJA> >
LJA> >
LJA> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
LJA> <html>
LJA> <head>
LJA> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
LJA> <title></title>
LJA> </head>
LJA> <body bgcolor="#ffffff" text="#000000">
LJA> The DatabaseMetaData method supportsConvert is used to validate what
LJA> the scalar escape function CONVERT can be used for based on the
LJA> driver/database combo.<br>
LJA> <br>
LJA> The javadoc for the supportsConvert(arg1, arg2) should clarified a bit
LJA> more.<br>
LJA> <br>
LJA> As far as the name of the SQLTYPE for the Convert scalar function,
LJA> drivers were doing this in an inconsistant manner. adding the SQL_
LJA> prefix brings it in line with ODBC. Drivers that do not support the
LJA> SQL_ prefix (some drivers support with and without the prefix), will be
LJA> required to support the prefix and to continue to optional support
LJA> without the prefix. <br>
LJA> <br>
LJA> Is there an additional question here that i might have missed?<br>
LJA> <br>
LJA> -lance<br>
LJA> <br>
LJA> Dag H. Wanvik wrote:<br>
LJA> <blockquote cite="mid0IJB008TKZLK4E@epost-mail1.sweden.sun.com"
LJA> type="cite">
LJA> <pre wrap="">Hi,
LJA>
LJA> (Lance, see question to you below)
LJA>
LJA> </pre>
LJA> <blockquote type="cite">
LJA> <blockquote type="cite">
LJA> <blockquote type="cite">
LJA> <blockquote type="cite">
LJA> <blockquote type="cite">
LJA> <pre wrap="">"DJD" == Daniel John Debrunner <a class="moz-txt-link-rfc2396E" href="mailto:djd@debrunners.com"><djd@debrunners.com></a> wrote:
LJA> </pre>
LJA> </blockquote>
LJA> </blockquote>
LJA> </blockquote>
LJA> </blockquote>
LJA> </blockquote>
LJA> <pre wrap=""><!---->DJD>
LJA> DJD> Dag H. Wanvik wrote:
LJA> DJD> > DJD> There's some inconsistency here, the ResultSet getter methods are
LJA> DJD> > DJD> converting from SQL data types to Java data types. This supportsConvert
LJA> DJD> > DJD> method takes two arguments, both of which describe SQL data types.
LJA> DJD> >
LJA> DJD> > Yes, you are right. Something for Lance to clarify :)
LJA> DJD> > But it would seem the no-args supportsConvert() should return false
LJA> DJD> > until we add support for CONVERT.
LJA> DJD>
LJA> DJD> And just to be clear, this is the JDBC CONVERT function from section C.5
LJA> DJD> of JDBC 3.0, correct?
LJA>
LJA> Yes.
LJA>
LJA> DJD>
LJA> DJD> I think there is some issue with CONVERT in JDBC 4.0, where the format
LJA> DJD> of the second argument is changing, from INTEGER to SQL_INTEGER or
LJA> DJD> something like that?
LJA>
LJA> Hmm.. I did a short check.. The DataBaseMetaData.supportsConvert has
LJA> int (from java.sql.Types aka JDBC types/SQLtypes) for both arguments
LJA> (both in JDBC 3.0 and early draft 4.0), which makes sense since the
LJA> API speaks of describing the support/behavior of CONVERT, and this
LJA> conversion all happens in the SQL domain.
LJA>
LJA> [On a side note: actually the Javadoc for supportsConvert speaks of
LJA> (unqualified) CONVERT, without being explicit on this being the C.5
LJA> escape JDBC CONVERT, not the SQL character set CONVERT, but I guess
LJA> that's kind of obvious..?]
LJA>
LJA> Also, in both the JDBC 3.0 and 4.0 spec, the escape function CONVERT
LJA> has SQLtype as the second argument, "value" being given as the first.
LJA>
LJA> The PreparedStatement "setter"/ ResultSet "getter" functions mappings,
LJA> though, convert from and to Java types, given by the tables in the B
LJA> appendix.
LJA>
LJA> I think the problem is that section 15.2.3.1 in the JDBC 4.0 spec
LJA> (14.2.3.1 in 3.0) erroneously states that
LJA> DataBaseMetaData.supportsConvert says ANYTHING about the mapping for
LJA> getter methods. Interestingly, the corresponding section on conversion
LJA> for *setter* methods makes no mention of
LJA> DataBaseMetaData.supportsConvert (section 13.2.2.1 in 4.0 as well as
LJA> in 3.0). Nor do the IN, OUT, INOUT descriptions.
LJA>
LJA> </pre>
LJA> <blockquote type="cite">
LJA> <pre wrap="">15.2.3.1 Data Type Conversions
LJA> The recommended ResultSet getter method for each JDBC type is shown
LJA> in TABLE B-6 on page B-210. This table also shows all of the
LJA> possible conversions that a JDBC driver may support. The method
LJA> DataBaseMetaData.supportsConvert(int fromType, int toType) returns
LJA> </pre>
LJA> </blockquote>
LJA> <pre wrap=""><!---->************************************
LJA> </pre>
LJA> <blockquote type="cite">
LJA> <pre wrap="">true if the driver supports the given conversion.
LJA> </pre>
LJA> </blockquote>
LJA> <pre wrap=""><!---->
LJA> Lance, do you agree this is wrong? If it is correct, please explain
LJA> what I am missing here..!
LJA>
LJA> Notwhithstanding this, the Derby implementation of no-args
LJA> DataBaseMetaData.supportsConvert() returns true, indicating we support
LJA> C.5 CONVERT, which we do not AFAICS, and I suggest we make a JIRA for
LJA> that.
LJA>
LJA> Dag
LJA> </pre>
LJA> </blockquote>
LJA> </body>
LJA> </html>
LJA>
--
Dag H. Wanvik
Sun Microsystems, Web Services, Database Technology Group
Haakon VII gt. 7b, N-7485 Trondheim, Norway
Tel: x43496/+47 73842196, Fax: +47 73842101
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact
the sender by reply email and destroy all copies of the original
message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Re: [jira] Created: (DERBY-447) getBoolean() throws data conversion
exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Lance J. Andersen" <La...@Sun.COM>.
The DatabaseMetaData method supportsConvert is used to validate what the
scalar escape function CONVERT can be used for based on the
driver/database combo.
The javadoc for the supportsConvert(arg1, arg2) should clarified a bit more.
As far as the name of the SQLTYPE for the Convert scalar function,
drivers were doing this in an inconsistant manner. adding the SQL_
prefix brings it in line with ODBC. Drivers that do not support the
SQL_ prefix (some drivers support with and without the prefix), will be
required to support the prefix and to continue to optional support
without the prefix.
Is there an additional question here that i might have missed?
-lance
Dag H. Wanvik wrote:
>Hi,
>
>(Lance, see question to you below)
>
>
>
>>>>>>"DJD" == Daniel John Debrunner <dj...@debrunners.com> wrote:
>>>>>>
>>>>>>
>DJD>
>DJD> Dag H. Wanvik wrote:
>DJD> > DJD> There's some inconsistency here, the ResultSet getter methods are
>DJD> > DJD> converting from SQL data types to Java data types. This supportsConvert
>DJD> > DJD> method takes two arguments, both of which describe SQL data types.
>DJD> >
>DJD> > Yes, you are right. Something for Lance to clarify :)
>DJD> > But it would seem the no-args supportsConvert() should return false
>DJD> > until we add support for CONVERT.
>DJD>
>DJD> And just to be clear, this is the JDBC CONVERT function from section C.5
>DJD> of JDBC 3.0, correct?
>
>Yes.
>
>DJD>
>DJD> I think there is some issue with CONVERT in JDBC 4.0, where the format
>DJD> of the second argument is changing, from INTEGER to SQL_INTEGER or
>DJD> something like that?
>
>Hmm.. I did a short check.. The DataBaseMetaData.supportsConvert has
>int (from java.sql.Types aka JDBC types/SQLtypes) for both arguments
>(both in JDBC 3.0 and early draft 4.0), which makes sense since the
>API speaks of describing the support/behavior of CONVERT, and this
>conversion all happens in the SQL domain.
>
>[On a side note: actually the Javadoc for supportsConvert speaks of
>(unqualified) CONVERT, without being explicit on this being the C.5
>escape JDBC CONVERT, not the SQL character set CONVERT, but I guess
>that's kind of obvious..?]
>
>Also, in both the JDBC 3.0 and 4.0 spec, the escape function CONVERT
>has SQLtype as the second argument, "value" being given as the first.
>
>The PreparedStatement "setter"/ ResultSet "getter" functions mappings,
>though, convert from and to Java types, given by the tables in the B
>appendix.
>
>I think the problem is that section 15.2.3.1 in the JDBC 4.0 spec
>(14.2.3.1 in 3.0) erroneously states that
>DataBaseMetaData.supportsConvert says ANYTHING about the mapping for
>getter methods. Interestingly, the corresponding section on conversion
>for *setter* methods makes no mention of
>DataBaseMetaData.supportsConvert (section 13.2.2.1 in 4.0 as well as
>in 3.0). Nor do the IN, OUT, INOUT descriptions.
>
>
>
>>15.2.3.1 Data Type Conversions
>>The recommended ResultSet getter method for each JDBC type is shown
>>in TABLE B-6 on page B-210. This table also shows all of the
>>possible conversions that a JDBC driver may support. The method
>>DataBaseMetaData.supportsConvert(int fromType, int toType) returns
>>
>>
>************************************
>
>
>>true if the driver supports the given conversion.
>>
>>
>
>Lance, do you agree this is wrong? If it is correct, please explain
>what I am missing here..!
>
>Notwhithstanding this, the Derby implementation of no-args
>DataBaseMetaData.supportsConvert() returns true, indicating we support
>C.5 CONVERT, which we do not AFAICS, and I suggest we make a JIRA for
>that.
>
>Dag
>
>
Re: [jira] Created: (DERBY-447) getBoolean() throws data conversion
exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Hi,
(Lance, see question to you below)
>>>>> "DJD" == Daniel John Debrunner <dj...@debrunners.com> wrote:
DJD>
DJD> Dag H. Wanvik wrote:
DJD> > DJD> There's some inconsistency here, the ResultSet getter methods are
DJD> > DJD> converting from SQL data types to Java data types. This supportsConvert
DJD> > DJD> method takes two arguments, both of which describe SQL data types.
DJD> >
DJD> > Yes, you are right. Something for Lance to clarify :)
DJD> > But it would seem the no-args supportsConvert() should return false
DJD> > until we add support for CONVERT.
DJD>
DJD> And just to be clear, this is the JDBC CONVERT function from section C.5
DJD> of JDBC 3.0, correct?
Yes.
DJD>
DJD> I think there is some issue with CONVERT in JDBC 4.0, where the format
DJD> of the second argument is changing, from INTEGER to SQL_INTEGER or
DJD> something like that?
Hmm.. I did a short check.. The DataBaseMetaData.supportsConvert has
int (from java.sql.Types aka JDBC types/SQLtypes) for both arguments
(both in JDBC 3.0 and early draft 4.0), which makes sense since the
API speaks of describing the support/behavior of CONVERT, and this
conversion all happens in the SQL domain.
[On a side note: actually the Javadoc for supportsConvert speaks of
(unqualified) CONVERT, without being explicit on this being the C.5
escape JDBC CONVERT, not the SQL character set CONVERT, but I guess
that's kind of obvious..?]
Also, in both the JDBC 3.0 and 4.0 spec, the escape function CONVERT
has SQLtype as the second argument, "value" being given as the first.
The PreparedStatement "setter"/ ResultSet "getter" functions mappings,
though, convert from and to Java types, given by the tables in the B
appendix.
I think the problem is that section 15.2.3.1 in the JDBC 4.0 spec
(14.2.3.1 in 3.0) erroneously states that
DataBaseMetaData.supportsConvert says ANYTHING about the mapping for
getter methods. Interestingly, the corresponding section on conversion
for *setter* methods makes no mention of
DataBaseMetaData.supportsConvert (section 13.2.2.1 in 4.0 as well as
in 3.0). Nor do the IN, OUT, INOUT descriptions.
> 15.2.3.1 Data Type Conversions
> The recommended ResultSet getter method for each JDBC type is shown
> in TABLE B-6 on page B-210. This table also shows all of the
> possible conversions that a JDBC driver may support. The method
> DataBaseMetaData.supportsConvert(int fromType, int toType) returns
************************************
> true if the driver supports the given conversion.
Lance, do you agree this is wrong? If it is correct, please explain
what I am missing here..!
Notwhithstanding this, the Derby implementation of no-args
DataBaseMetaData.supportsConvert() returns true, indicating we support
C.5 CONVERT, which we do not AFAICS, and I suggest we make a JIRA for
that.
Dag
Re: [jira] Created: (DERBY-447) getBoolean() throws data conversion
exception for DECIMAL type in J2ME/CDC/Foundation
Posted by Daniel John Debrunner <dj...@debrunners.com>.
Dag H. Wanvik wrote:
> DJD> There's some inconsistency here, the ResultSet getter methods are
> DJD> converting from SQL data types to Java data types. This supportsConvert
> DJD> method takes two arguments, both of which describe SQL data types.
>
> Yes, you are right. Something for Lance to clarify :)
> But it would seem the no-args supportsConvert() should return false
> until we add support for CONVERT.
And just to be clear, this is the JDBC CONVERT function from section C.5
of JDBC 3.0, correct?
I think there is some issue with CONVERT in JDBC 4.0, where the format
of the second argument is changing, from INTEGER to SQL_INTEGER or
something like that?
Dan.
Re: [jira] Created: (DERBY-447) getBoolean() throws data conversion
exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Hi again,
>>>>> "DJD" == Daniel John Debrunner <dj...@debrunners.com> wrote:
DJD> > public boolean supportsConvert() {
DJD> > return true;
DJD> > }
DJD> >
DJD> > public boolean supportsConvert(int fromType, int toType) {
DJD> > /*
DJD> > * at the moment we don't support CONVERT at all, so we take the easy
DJD> > * way out. Eventually we need to figure out how to handle this
DJD> > * cleanly.
DJD> > */
DJD> > return false;
DJD> >
DJD> > JDBC 3.0 section 14.2.3.1 "Data Type Conversions" says this method
DJD> > should return true if the driver supports the respective getter method
DJD> > on the result set.
DJD>
DJD> There's some inconsistency here, the ResultSet getter methods are
DJD> converting from SQL data types to Java data types. This supportsConvert
DJD> method takes two arguments, both of which describe SQL data types.
Yes, you are right. Something for Lance to clarify :)
But it would seem the no-args supportsConvert() should return false
until we add support for CONVERT.
Dag
Re: [jira] Created: (DERBY-447) getBoolean() throws data conversion
exception for DECIMAL type in J2ME/CDC/Foundation
Posted by Daniel John Debrunner <dj...@debrunners.com>.
Dag H. Wanvik wrote:
> Hi,
>
> Out of curiosity I checked the DatabaseMetaData on the topic of
> conversion and I found that supportsConvert() returns true, but still
> returns false for all combination of types,
> e.g. supportsConvert(java.sql.Types.DECIMAL, java.sql.Types.BOOLEAN);
> viz. the code in the embedded driver:
>
> public boolean supportsConvert() {
> return true;
> }
>
> public boolean supportsConvert(int fromType, int toType) {
> /*
> * at the moment we don't support CONVERT at all, so we take the easy
> * way out. Eventually we need to figure out how to handle this
> * cleanly.
> */
> return false;
>
> JDBC 3.0 section 14.2.3.1 "Data Type Conversions" says this method
> should return true if the driver supports the respective getter method
> on the result set.
There's some inconsistency here, the ResultSet getter methods are
converting from SQL data types to Java data types. This supportsConvert
method takes two arguments, both of which describe SQL data types.
Dan.
Re: [jira] Created: (DERBY-447) getBoolean() throws data conversion
exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Hi,
Out of curiosity I checked the DatabaseMetaData on the topic of
conversion and I found that supportsConvert() returns true, but still
returns false for all combination of types,
e.g. supportsConvert(java.sql.Types.DECIMAL, java.sql.Types.BOOLEAN);
viz. the code in the embedded driver:
public boolean supportsConvert() {
return true;
}
public boolean supportsConvert(int fromType, int toType) {
/*
* at the moment we don't support CONVERT at all, so we take the easy
* way out. Eventually we need to figure out how to handle this
* cleanly.
*/
return false;
JDBC 3.0 section 14.2.3.1 "Data Type Conversions" says this method
should return true if the driver supports the respective getter method
on the result set.
The Javadoc for the method *only* talks about the CONVERT function
(JDBC 3.0 App C.5), though, and since we don't implement that yet (?),
I guess that's the reason we return false above.
I suppose there are three issues here:
a) We don't yet support CONVERT (improvement?)
b) We do support conversion on getter methods for result sets, but
the "supportsConvert" doesn't reflect that (bug?)
c) supportsConvert() (with no args) returns true (not true!) (bug?)
I could not find any JIRA issue on any of these, nor the did I find
anything about it in the docs.
It may seem we need to implement explicit CONVERT *or* drop getter
method conversion (for those conversions we do support) to be in
compliance? Comments?
Dag
>>>>> "DR(" == Deepa Remesh (JIRA) <de...@db.apache.org> wrote:
DR(>
DR(> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
DR(> -------------------------------------------------------------------------------------
DR(>
DR(> Key: DERBY-447
DR(> URL: http://issues.apache.org/jira/browse/DERBY-447
DR(> Project: Derby
DR(> Type: Bug
DR(> Components: JDBC
DR(> Reporter: Deepa Remesh
DR(> Assigned to: Deepa Remesh
DR(>
DR(>
DR(> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
DR(>
DR(> --
DR(> This message is automatically generated by JIRA.
DR(> -
DR(> If you think it was sent incorrectly contact one of the administrators:
DR(> http://issues.apache.org/jira/secure/Administrators.jspa
DR(> -
DR(> For more information on JIRA, see:
DR(> http://www.atlassian.com/software/jira
DR(>
--
Dag H. Wanvik
Sun Microsystems, Web Services, Database Technology Group
Haakon VII gt. 7b, N-7485 Trondheim, Norway
Tel: x43496/+47 73842196, Fax: +47 73842101
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact
the sender by reply email and destroy all copies of the original
message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[jira] Updated: (DERBY-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Daniel John Debrunner updated DERBY-447:
----------------------------------------
Version: 10.1.1.0
10.2.0.0
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0, 10.2.0.0
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Deepa Remesh closed DERBY-447:
------------------------------
Resolution: Fixed
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0, 10.2.0.0
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Fix For: 10.2.0.0, 10.1.2.0, 10.1.1.1
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Deepa Remesh updated DERBY-447:
-------------------------------
Attachment: derby-447_2.diff
Hi Dan,
Thanks for pointing this out. I was using a round-about way to check if the value is null. Please look at the re-submitted patch.
Deepa
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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] Reopened: (DERBY-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Daniel John Debrunner reopened DERBY-447:
-----------------------------------------
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0, 10.2.0.0
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Fix For: 10.2.0.0, 10.1.1.0
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Daniel John Debrunner closed DERBY-447:
---------------------------------------
Resolution: Fixed
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0, 10.2.0.0
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Fix For: 10.2.0.0, 10.1.1.0
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=comments#action_12315278 ]
Daniel John Debrunner commented on DERBY-447:
---------------------------------------------
Rather than this code
String bigDecimalString = getString();
if(bigDecimalString == null)
return false;
to see if the value is NULL, you should use the isNull() method. e.g.
if (isNull())
return false;
otherwise it looks good. Can you re-submit a patch?
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Attachments: derby-447.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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] Reopened: (DERBY-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Kathey Marsden reopened DERBY-447:
----------------------------------
reopening to fix fix in
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0, 10.2.0.0
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Fix For: 10.2.0.0, 10.1.2.0
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=comments#action_12315962 ]
Daniel John Debrunner commented on DERBY-447:
---------------------------------------------
Committed revision 219260 on 10.1 branch (merge of 209845)
svn merge -r 209844:209845 https://svn.apache.org/repos/asf/incubator/derby/code/trunk/
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0, 10.2.0.0
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Fix For: 10.2.0.0
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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] Resolved: (DERBY-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Kathey Marsden resolved DERBY-447:
----------------------------------
Fix Version: 10.1.2.0
(was: 10.1.1.0)
Resolution: Fixed
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0, 10.2.0.0
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Fix For: 10.2.0.0, 10.1.2.0
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Daniel John Debrunner updated DERBY-447:
----------------------------------------
Fix Version: 10.2.0.0
Committed revision 209845.
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0, 10.2.0.0
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Fix For: 10.2.0.0
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Deepa Remesh updated DERBY-447:
-------------------------------
Attachment: derby-447.diff
This patch implements getBoolean() method in BigIntegerDecimal, which is the class used for DECIMAL support in J2ME/CDC/Foundation. The method returns false for zero or null values and true for all other values.
Here is the method implementation:
// 0 or null is false, all else is true
public boolean getBoolean()
{
String bigDecimalString = getString();
if(bigDecimalString == null)
return false;
BigInteger bi = new BigInteger(data2c);
return bi.compareTo(java.math.BigInteger.ZERO) != 0;
}
I ran the test jdbcapi/resultset.java using IBM WCTME5.7 Foundation profile. Before the change the output file resultset.out had the following output for calls to getBoolean() for DECIMAL values:
getBoolean(10) got exception
Data Conversion SQLException
getBoolean(dc) got exception
Data Conversion SQLException
After the change, getBoolean() for DECIMAL value does not throw data conversion exception. The output file now has:
getBoolean(10): true
getBoolean(dc): true
To verify that the getBoolean() method returns the right value, I also tested using the following DECIMAL values (-10.1, 0, -0, 0.00, -0.00, null).
Note: The test jdbcapi/resultset.java is currently excluded for J2ME/Foundation. The following line "runwithfoundation=false" in resultset_app.properties has to be commented to be able to run the test. Also, the test will not be successful because of other BigDecimal methods. So the specific lines in output has to be checked in resultset.out. I am working on a test wrapper to make the test work in J2ME/Foundation and will submit this in a separate task.
Please review this patch and commit it.
Thanks,
Deepa
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Attachments: derby-447.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Deepa Remesh closed DERBY-447:
------------------------------
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0, 10.2.0.0
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Fix For: 10.2.0.0
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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] Reopened: (DERBY-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Deepa Remesh reopened DERBY-447:
--------------------------------
reopening to fix fix version
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0, 10.2.0.0
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Fix For: 10.2.0.0, 10.1.2.0
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Daniel John Debrunner updated DERBY-447:
----------------------------------------
Fix Version: 10.1.1.0
Also marked fixed in 10.1 branch
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0, 10.2.0.0
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Fix For: 10.2.0.0, 10.1.1.0
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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] Resolved: (DERBY-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Deepa Remesh resolved DERBY-447:
--------------------------------
Resolution: Fixed
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0, 10.2.0.0
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Fix For: 10.2.0.0
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Deepa Remesh updated DERBY-447:
-------------------------------
Fix Version: 10.1.1.1
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0, 10.2.0.0
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Fix For: 10.2.0.0, 10.1.2.0, 10.1.1.1
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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-447) getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-447?page=all ]
Kathey Marsden closed DERBY-447:
--------------------------------
> getBoolean() throws data conversion exception for DECIMAL type in J2ME/CDC/Foundation
> -------------------------------------------------------------------------------------
>
> Key: DERBY-447
> URL: http://issues.apache.org/jira/browse/DERBY-447
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0, 10.2.0.0
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Fix For: 10.2.0.0, 10.1.2.0
> Attachments: derby-447_2.diff
>
> The call to the ResultSet method getBoolean() for a DECIMAL value throws data conversion exception with J2ME/CDC/Foundation. The class BigIntegerDecimal, which is used for DECIMAL support in J2ME/CDC/Foundation, does not override the getBoolean() method from the class DataType. The getBoolean() method in DataType simply throws a data conversion exception.
--
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