Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: Mick Fong <Mick.Fong@kti.wa.edu.au>
To: "'user@cayenne.apache.org'" <user@cayenne.apache.org>
Subject: RE: java.sql.SQLException: Unknown Types value
Thread-Topic: java.sql.SQLException: Unknown Types value
Thread-Index: Ac5svVj1IsCz2j41Q0aYDJsXSiDkJv//4NsAgAFHgY6AAEbAAIAAcuoA//7QKgA=
Date: Fri, 21 Jun 2013 06:16:35 +0000
Message-ID: <A62B0A6D6B5FA04D81F31BCDF6960D1D08B7113D@brm-10.kimberley.local>
References: <A62B0A6D6B5FA04D81F31BCDF6960D1D08B70016@brm-10.kimberley.local>
 <CAA-upzojOM+USTXzomcC6Ek_AnutTic63yU49T-P000fBz61EQ@mail.gmail.com>
 <A62B0A6D6B5FA04D81F31BCDF6960D1D08B7109D@brm-10.kimberley.local>
 <CAA-upzqwk+PFt_wJQHtbDuaQNG_+Un_FpiFSMCds8NW9=L9y_w@mail.gmail.com>
 <C894BDF1-E5E0-4BF4-B958-AF38ABD43CB6@objectstyle.org>
In-Reply-To: <C894BDF1-E5E0-4BF4-B958-AF38ABD43CB6@objectstyle.org>
Accept-Language: en-US, en-AU
Content-Language: en-US
Content-Type: multipart/mixed;
	boundary="_002_A62B0A6D6B5FA04D81F31BCDF6960D1D08B7113Dbrm10kimberleyl_"
MIME-Version: 1.0

--_002_A62B0A6D6B5FA04D81F31BCDF6960D1D08B7113Dbrm10kimberleyl_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Andrus,

Yes I am running, 3.0.2 (on windows).

The type value I get is "2147483647" (which is the max int obviously)

Attached image shows it in the debugger.


cheers

Mick Fong
Simulator Engineer
=A0
p (08) 9193 8921
m=A00413 113 099
f (08) 9192 9111
e mick.fong@kti.wa.edu.au
a PO Box 1380, Broome WA 6725

-----Original Message-----
From: Andrus Adamchik [mailto:andrus@objectstyle.org]=20
Sent: Friday, 21 June 2013 4:05 AM
To: user@cayenne.apache.org
Subject: Re: java.sql.SQLException: Unknown Types value

>From checking the sources, I am also assuming 3.0.*:

    public void setJdbcObject(
            PreparedStatement st,
            Object value,
            int pos,
            int type,
            int scale) throws Exception {

        // if this is a CLOB column, set the value as "String"
        // instead. This should work with most drivers
        if (type =3D=3D Types.CLOB) {
            st.setString(pos, (String) value);
        }
        else if (scale !=3D -1) {
            st.setObject(pos, value, type, scale);
        }
        else {
           // THIS IS LINE 169
            st.setObject(pos, value, type);
        }
    }

Mick, Could you possibly run this in debugger and tell us what the value of=
 the "type" variable is?

Andrus


On Jun 20, 2013, at 9:13 AM, Michael Gentry <mgentry@masslight.net> wrote:

> Hi Mick,
>=20
> Did you maybe map a CHAR in your Cayenne DbEntity to a VARCHAR column=20
> or vice-versa?  I could see this causing a problem.
>=20
> We use views just fine with Cayenne and have both CHAR and VARCHAR=20
> mappings (to the appropriate DB types) in Cayenne 3.0.  You didn't=20
> mention which version of Cayenne you are using, so I'm guessing 3.0 curre=
ntly.
>=20
> mrg
>=20
>=20
>=20
> On Wed, Jun 19, 2013 at 9:11 PM, Mick Fong <Mick.Fong@kti.wa.edu.au> wrot=
e:
>=20
>> Hi Michael,
>>=20
>> The type is definitely a varchar in the view.
>>=20
>> The error is when the you are setting the query object for the=20
>> PreparedStatement. It appears that the=20
>> org.apache.cayenne.access.types.CharType is not being recognised as a=20
>> MySQL varchar type.
>>=20
>> The exception is thrown from a switch on the parameter SQL type:
>>=20
>> switch (targetSqlType) {
>>  .
>>  .
>>  case Types.CHAR:
>>  case Types.VARCHAR:
>>  case Types.LONGVARCHAR:
>>    if (parameterObj instanceof BigDecimal) {
>>=20
>> setString(parameterIndex,(StringUtils.fixDecimalExponent(StringUtils.
>> consistentToString((BigDecimal)
>> parameterObj))));
>>    } else {
>>      setString(parameterIndex, parameterObj.toString());
>>    }
>>=20
>>  break;
>>  .
>>  .
>>  default:
>>    throw
>> SQLError.createSQLException(Messages.getString("PreparedStatement.16"
>> ),
>> //$NON-NLS-1$
>>      SQLError.SQL_STATE_GENERAL_ERROR, getExceptionInterceptor()); }
>>=20
>>=20
>> The property value for the message is:
>> PreparedStatement.16=3DUnknown Types value
>>=20
>>=20
>> The error occurs just when setting the parameters because the=20
>> CharType is not recognised.
>>=20
>> thanks
>>=20
>> mick
>>=20
>> [Kimberley Training Institute Logo]
>> Toll Free: 1300 996 573 | Website: www.kti.wa.edu.au<=20
>> http://www.kti.wa.edu.au> Find us on=20
>> Facebook<http://www.facebook.com/kimberleytraininginstitute>
>>=20
>> Please consider the environment before printing this email.
>>=20


--_002_A62B0A6D6B5FA04D81F31BCDF6960D1D08B7113Dbrm10kimberleyl_--