Hello everyone,

Could you share your approach to concurrency in combination with cl-prevalence?

As far as I understand, simultaneous transactions (IOW modifications) of the database are impossible, because all transactions use the same transaction log file and therefore must happen sequentially to avoid the transaction log corruption caused by concurrent writes.

What about reading operations for persistent data? Has anyone implemented multiple-read/single write locking?

Or you don't care and just user one global lock for all your database?

Best regards, - Anton