Re: Best way to inform (and handle cached object refreshing) of externally-updated database records?

From: Mike Kienenberger (mkienen..laska.net)
Date: Mon Nov 22 2004 - 15:53:47 EST

  • Next message: Alex Gunawan Wibowo: "CayenneModeler's Reengineer + MySQL server"

    To answer some of my own questions...

    (with as much chance of correctness as when I answer anyone else's (-: )

    Mike Kienenberger <mkienen..laska.net> wrote:
    > I'm not sure of the implications
    > of one session invalidating objects in all other active sessions. Reading

    > the source indicates that new objects won't be touched, but makes me think

    > that any changes in a modified object would be lost. Would this be true?

    It seems to be that this would be true, so globally invalidating an object
    could lose changes-in-progress.

    > I'm also unclear what would happen when I import an object from
    > another session using context.localObjects().

    Looking at the source seems to indicate that all objects imported into a
    session are marked hollow, so that shouldn't be a problem.



    This archive was generated by hypermail 2.0.0 : Mon Nov 22 2004 - 15:52:13 EST