• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: quick followup: ERXExistsQualifier blocks *all coordinators* even before a SELECT?!?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: quick followup: ERXExistsQualifier blocks *all coordinators* even before a SELECT?!?


  • Subject: Re: quick followup: ERXExistsQualifier blocks *all coordinators* even before a SELECT?!?
  • From: Samuel Pelletier <email@hidden>
  • Date: Sat, 15 Oct 2016 20:53:39 -0400

Hi OC,

You may also try to fetch without the exists qualifier and apply it in memory on the fetched objects to see if the locking will append too.

I looked a bit into the code and there is at least a global lock involved in the execution, EOModel._EOGlobalModelLock. These are in methods to get informations about the model so I expect the lock to be very shorts

If you can create a repeatable case and be able to suspend the program during the pause, you will at least be able to find out where it append.

There is probably better way to investigate locking problems but I do not know them.

Regards,

Samuel


> Le 13 oct. 2016 à 12:39, OC <email@hidden> a écrit :
>
> To be sure where the delay happens, I have tried to re-write the code [1] to
>
> === 1 ===
> def me=new EOKeyValueQualifier('user',EOQualifier.QualifierOperatorEqual,sess.currentUser)
> def hasme=new ERXExistsQualifier(me,'userLinks')
> def fs=new EOFetchSpecification('DBGenGeneratedItem',hasme,null)
> NSLog.err.appendln "FETCH STARTS..."
> all=session.defaultEditingContext().objectsWithFetchSpecification(fs)
> NSLog.err.appendln "... FETCH DID END"
> ===
>
> and still the delay (which looks like waiting for the beackground threads) happens in betwixt "FETCH STARTS" and "=== Begin Internal Transaction".
>
> Thus, it is self-evident it happens somewhere in objectsWithFetchSpecification, if (and only if!) the qualifier contains ERXExistsQualifier.
>
>
> _______________________________________________
> 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


 _______________________________________________
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


References: 
 >ERXExistsQualifier blocks *all coordinators* even before a SELECT?!? (From: "email@hidden" <email@hidden>)
 >quick followup: ERXExistsQualifier blocks *all coordinators* even before a SELECT?!? (From: OC <email@hidden>)

  • Prev by Date: Postgres double connection: fixed
  • Next by Date: Re: Maven and eclipse #2 - problem with missing bundle? null mainBundleName()
  • Previous by thread: quick followup: ERXExistsQualifier blocks *all coordinators* even before a SELECT?!?
  • Next by thread: new to AWS
  • Index(es):
    • Date
    • Thread