Re: DataContext.registerNewObject() vs. entityResolver

From: Holger Hoffstätte (holge..izards.de)
Date: Mon Nov 18 2002 - 15:47:37 EST

  • Next message: Craig Miskell: "Insert order of DBEntities"

    Holger Hoffstätte wrote:
    > - keep register(DataObject)
    > - keep the register(DataObject, String) method deprecated
    > - create register(DataObject, ObjEntity) instead

    Sent this follow-up to Craig only, not to the list - sorry.

    --snip--

    Hi Craig

    > That seems a little cleaner to me (than the previously mooted
    > solutions). It's in keeping with the recent changes moving away from
    > Strings *most* of the time, but still gives the alternative option.

    Yup. But as you noted (and dawned on me just 1 minute after implementing),
    it doesn't really win you anything. People who clutter their code with
    Strings will just clutter it up with String-based lookups - people who
    have to use Strings because they have the EOGenericRecord case on their
    hands will probably put the entity name in a single global String anyway,
    simply because it's good practice.

    I guess the easiest thing will be to just de-deprecate the
    register(DataObject, String) method, fix everything up so that the tests
    work again (I already did all that, just have to commit) and spend time on
    more important things, like fixing bugs or the unused variables.

    -h



    This archive was generated by hypermail 2.0.0 : Mon Nov 18 2002 - 15:47:55 EST