Expected Behavior

1. Prevent a deploy from being executed if one of the physical schemas requested for deployment is already being deployed to by another process

2. Allow a timeout to be specified so that we don't have a case where a process exits and doesn't "unlock" the deployment

3. Ensure that "unlocking" happens on shutdown hook if needed

4. Try to check on active processes via some approach, whether by checking the PID of the deploy process or the connection number

5. The above assume a pessimistic lock. Brainstorm if optimistic lock could work? However, DBMS types like Sybase IQ by default will lock a whole table on a write, making optimistic locking difficult in practice

Actual Behavior

No such lock behavior exists

Obevo Version where this issue was observed

All versions lack this feature

Steps to reproduce

Try in an in-memory db?