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

2016-10-15 Thread Samuel Pelletier
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

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

2016-10-13 Thread OC
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

ERXExistsQualifier blocks *all coordinators* even before a SELECT?!?

2016-10-13 Thread o...@ocs.cz
Hello there, just the very now, I have bumped into a weird problem. I run some DB-intensive background tasks. So as they do not block the whole application, I set up er.extensions.ERXObjectStoreCoordinatorPool.maxCoordinators > 1, and my code (a) gives one of the coordinators to all sessions (