new 1.2-M11 bug: "uniquing" seems broken

From: Mike Kienenberger (mkienen..mail.com)
Date: Wed Apr 12 2006 - 14:39:27 EDT

  • Next message: Andrus Adamchik: "Re: new 1.2-M11 bug: "uniquing" seems broken"

    I will try this again in a moment with the latest SVN snapshot, but
    uniquing appears to be broken. Has this been fixed since 1.2-M11?

    I have two instances of <ObjectId:Address, ADDRESS_ID=1683> in both
    the modified and committed state in the same data context.

    this= Address (id=145)
            objectContext= DataContext (id=158)
            objectId= ObjectId (id=163)
            persistenceState= 3
            snapshotVersion= -9223372036854769899
            values= HashMap (id=165)
    arg0= Address (id=90)
            objectContext= DataContext (id=158)
            objectId= ObjectId (id=170)
            persistenceState= 4
            snapshotVersion= -9223372036854769889
            values= HashMap (id=171)

    if (contact.getMailingAddress().equals(mailingAddress))

    this= Address (id=145)

    {<ObjectId:Address, ADDRESS_ID=1683>; committed;
    [contactPhysicalAddressList=>?; contactMailingAddressList=>(..);
    description=>Mailing; streetAddress=>660 Farmers Loop Rd. Fbks, Ak
    99712; streetNumber=>null; zip=>null; contactOtherAddressList=>?;
    city=>null; apt=>null]}

    arg0= Address (id=90)

    {<ObjectId:Address, ADDRESS_ID=1683>; modified; [stateProvince=>?;
    contactPhysicalAddressList=>?; contactMailingAddressList=>?;
    description=>Mailing; streetNumber=>null; streetAddress=>660 Farmers
    Loop Rd. Fbks, Ak 99712; zip=>null; contactOtherAddressList=>?;
    city=>null; apt=>null]}



    This archive was generated by hypermail 2.0.0 : Wed Apr 12 2006 - 14:39:52 EDT