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

[Sebastien B. <sbi...@us...>]

Marcos Dione <md...@vi...> writes:
> User-Agent: Mutt/1.3.28i
>=20
> 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),=20
>=20
>     note that holding the globalID is the same that using the raw_row.

Yeap! except that gIDs have the minimum amount of information needed to
retrieve objects, while raw rows can have a much bigger memory footprint ;)

> 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 :)

Ok

>     anyways, the problem is not with from-db instances, but with new
> instances.
>=20
> > 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.
>=20
>     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.
>=20
> >   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.
>=20
>     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)?

If you can, sure: this would help to have the code triggering the bug at
hand --along with the instructions for reproducing and observing the
bug.

-- S=E9bastien.