Re: [Modeling-users] saveChanges() doesn't change globalID

[Marcos D. <md...@vi...>]

User-Agent: Mutt/1.3.28i

On Fri, Sep 10, 2004 at 12:42:30AM +0200, Sebastien Bigaret wrote:
>   I mean, if you simply drop the existing ECs and get a brand new one,
>   then ask it for the Persona() (either from a given fetch qualifier or
>   from its globalID), 

    note that holding the globalID is the same that using the raw_row.
the fetch qualifier wouldn't be useful, as the user could have selected
the Persona() fron la list (the result of a search). I realize you don't
know that part of the app yet :)

    anyways, the problem is not with from-db instances, but with new
instances.

> I suspect I'm missing something important here --because if you simply
> want to rollback, then you wouldn't try to (re) add newly inserted
> objects (PostallAddresses I guess) from the beginning.

    maybe, I haven't decided taht part, but forgetting them sounds
reasonable. for rollbacking limited instances we would prefer to obligue
the user to save the changes to a previous instance.

>   Now, whatever your use-cases are and what is behind, I want to make it
>   clear that, if this is the bug you're observing, this is a serious one
>   that should be addressed as quickly as possible.  If you do not have
>   the time to extract the behaviour but have some code revealing it that
>   you do not want to disclose on a public list, please email me
>   privately and we'll work together on making from your experience a
>   public test revealing the bug.

    well, I have code, but it's very buried in my app's code. unluckly I
don't have the time this weeken to try to untangle a simpler example,
and I don't know if my code's guilty. can I send you the whole bunch
(~140k)?

>     Thanks for your time!

    thanks for *yours*.