Re: UtilDateType materializeObject for non-date type

From: Andrus Adamchik (andru..bjectstyle.org)
Date: Fri Mar 12 2004 - 15:43:11 EST

  • Next message: Andriy Shapochka: "CayenneDataObject.read/writeProperty(...) protected vs public"

    On Mar 11, 2004, at 12:06 PM, Mike Kienenberger wrote:

    >
    > default :
    > val = rs.getObject(index);
    > break;
    >
    > Since a non-date/time type is going to throw a less-informative
    > ClassCastException anyway, why not point out the exact problem?
    > Otherwise,
    > when Oracle or someone switches to a non-conforming class (like in the
    > Oracle 8 to 9 upgrade), it's going to be less obvious what went wrong.

    Makes sense - I'll add an explicit check for the type of object
    returned here, and throw a more informative exception.

    Andrus

    This archive was generated by hypermail 2.0.0 : Fri Mar 12 2004 - 15:43:16 EST