All,

Serge tested removing the lock system from the DB layer.

All seems to work, as John indicated it would. He wins 20 min in import time, and off course no error that locks are exhausted.

See http://www.gramps-project.org/bugs/view.php?id=6459

Doug, do you need it for gramps-connect? I suppose not as we have the PRIVATE in it.

If you guys agree, I would suggest to:

1/add a gramps option to enable locking. Default is no locking
2/based on the option setting, apply the patch of that bug ticket

I would suggest an option because officially gramps is a python module, so we should allow other GUI or app to be made that uses multiple threads, and hence needs the locking.

Thoughts, ideas?

Benny