Re: Object Graph Refreshing: design ideas?

From: Andrus Adamchik (andru..bjectstyle.org)
Date: Fri Dec 19 2003 - 23:53:34 EST

  • Next message: Mike Kienenberger: "BUG?: performQuery() != {setFetchingDataRows(), objectFromDataRow(), performQuery()} for OpenBase time type"

    On Dec 19, 2003, at 11:48 PM, Andrus Adamchik wrote:

    > 1. "Kill Them All, Let God Sort Them Out":
    >
    > Currently sources of "indirect" relationships are marked as "MODIFIED"
    > and stay this way until ContextCommit figures out that there is
    > nothing to do in the DB, and changes them back to COMMITTED. We don't
    > know anything about the nature of modification to these objects. But
    > we can simply include their Ids in the event, and let the receiver
    > invalidate these objects, so that on the next access they will be
    > refetched, including all relationships. This is the most simple
    > solution and should work within the current design frame (I haven't
    > tried it yet though, so there maybe limitations). But it may result in
    > some serious overhead refetching lots of invalidated objects.

    Just discovered one limitation with that - we can't invalidate modified
    objects... But we can probably give users a way to handle this via a
    delegate....

    Andrus

    This archive was generated by hypermail 2.0.0 : Fri Dec 19 2003 - 23:53:39 EST