Re: Might perhaps ERXEnterpriseObject.updateInverseRelationships fail?
Re: Might perhaps ERXEnterpriseObject.updateInverseRelationships fail?
- Subject: Re: Might perhaps ERXEnterpriseObject.updateInverseRelationships fail?
- From: OCsite via Webobjects-dev <email@hidden>
- Date: Wed, 20 Sep 2023 13:48:09 +0200
Hmmmm, I've just got a bugreport from the production, and looks like we have
again bumped into the rare problem that (seemingly) sometimes
ERXEnterpriseObject.updateInverseRelationships fails to update the :N
relationship, as detailed below in my June e-mail.
Nobody happened to encounter a similar problem lately, or perhaps, even better,
find a culprit and fix that?
Thanks a lot!
OC
> On 7. 6. 2023, at 11:12, OCsite via Webobjects-dev
> <email@hidden> wrote:
>
> Hi there,
>
> pretty rarely, but alas repeatedly — something like, twice a year — our
> clients observe a weird behaviour that
> - they add “a row to a table”, means an eo into a standard 1:N relationship;
> - immediately after that, they do not see the newly added row in the GUI, nor
> do see it newly logged-in users, means their table.rows relationship does not
> contain the new one;
> - in awhile, or if the app happens to be restarted, immediately after the new
> launch, the problem disappears.
>
> Not surprisingly, so far we haven't found any way to trigger the problem
> intentionally :(
>
> We have never observed similar problem with other relationships — which might
> just as well mean it never happened, or that it does happen too, but just
> never got noticed so far :)
>
> I went repeatedly through the logs and so far found no reliable explanation,
> but eventually it occurred to me if
> ERXEnterpriseObject.updateInverseRelationships (which we use to keep all our
> relationships in sync) happened to fail somehow, it would, I believe, cause
> precisely the observed behaviour: the new object would be set up all right,
> it would get its proper :1 relationship to the table (the appropriate FK
> would be set and eventually saved to the DB all right), but the table's :N
> inverse, for some weird reason, would not get updated to contain the new
> object. New sessions (well all new ECs whichever way they are created) would
> get the wrong (not-updated) relationship from table to rows from the to-many
> snapshot, until the EC timestamp lag times out. When it does (or when the app
> gets relaunched), the relationships gets re-fetched from the database, which
> fixes the problem.
>
> My primary question is, has anybody lately observed any problems with
> ERXEnterpriseObject.updateInverseRelationships reliability?
>
> Thanks!
> OC
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden