Re: Strange insertion of UPPER when Ordering by TIMESTAMP in SQL Server

From: Andrus Adamchik (andru..bjectstyle.org)
Date: Wed Aug 11 2010 - 06:58:39 UTC

  • Next message: mr.abanjo: "Re: Get PK value of a previously generated object"

    I am afraid in this case it is a responsibility of the user to specify
    case sensitivity. Cayenne doesn't try to second guess here.

    Andrus

    On Aug 11, 2010, at 3:10 AM, Gary Jarrel wrote:

    >> Just curious, did you use SortOrder.DESCENDING_INSENSITIVE?
    >>
    >> mrg
    >>
    >>
    >
    > Yes that is the case, I've just had a look through my code and it is
    > being set. The reason though is that we have a small generic DAO
    > package which has methods such as
    >
    > findObjectsByParameters(Class<T> objectEntity, Map<?, ?> params,
    > OrderedMap<String, Boolean> ordering);
    >
    > It then build the query and executes it, however by default when
    > adding Ordering it uses SortOrder.ASCENDING_INSENSITIVE and
    > SortOrder.ASCENDING_INSENSITIVE,
    >
    > I would have thought that the the case insensitivity would be applied
    > only to String based fields and ignored for Date fields?
    >
    > Thank you
    >
    > Gary
    >

    This archive was generated by hypermail 2.0.0 : Wed Aug 11 2010 - 06:59:16 UTC