Re: Oracle ClassCast Exception

From: Mike Kienenberger (mkienen..laska.net)
Date: Wed Feb 16 2005 - 12:32:46 EST

  • Next message: Joćo Paulo Vasconcellos: "Re: Oracle ClassCast Exception"

    =?ISO-8859-1?Q?Jo=E3o_Paulo_Vasconcellos?= <vasconcello..mail.com> wrote:
    > Very good shot, I only get problems on tables with DATE fields...
    >
    > INFO QueryLogger: +++ Connecting: SUCCESS.
    > INFO QueryLogger: SELECT t0.DES_EMAIL, t0.DES_SUGESTAO,
    t0.NUM_SEQ_FALE_COM_DIX
    > AMICO FROM DIXSP.SUGESTAO_WEB t0
    > INFO QueryLogger: === returned 0 rows. - took 219 ms.
    > INFO QueryLogger: +++ no commit - transaction controlled externally.
    > INFO QueryLogger: --- will run 1 query.
    > INFO QueryLogger: SELECT t0.DES_EMAIL, t0.DES_SUGESTAO,
    t0.NUM_SEQ_FALE_COM_DIX
    > AMICO FROM DIXSP.SUGESTAO_WEB t0
    > INFO QueryLogger: === returned 0 rows. - took 16 ms.
    > INFO QueryLogger: +++ no commit - transaction controlled externally.
    >
    > All went fine.
    >
    > Correct me if I am wrong, a quickfix would be to change the default types
    in
    >
    > org.objectstyle.cayenne.dba.types.xml
    >
    > from DATE to TIMESTAMP, correct?

    TIMESTAMP is an Oracle 9 type, so that won't help you even if it's
    date-related. types.xml should already be correct for Oracle 8.
    I think you'll have to see what's going on at AbstractType.setJdbcObject().
    I don't see why it's date related since you're only doing setObject calls on
    NUMBER fields.



    This archive was generated by hypermail 2.0.0 : Wed Feb 16 2005 - 12:32:05 EST