Block DDL changes (CREATE TABLE or DROP TABLE commands) while queries are running concurrently
As mentioned in #90 (comment 270684740) (comment text pasted below), the idea is to use M locks to ensure the DDL change does not happen concurrently while queries are running.
YottaDB locks can be used to prevent a DDL change when there is a running query, and prevent new queries from starting when a DDL change is awaiting the end of running queries.
Draft Release Note
A CREATE TABLE or DROP TABLE waits for all concurrently running other queries (SELECT or CREATE TABLE or DROP TABLE) to finish so it can safely make DDL changes. It waits for an exclusive lock with a timeout of 10 seconds If it fails due to a timeout, the user needs to stop all concurrently running queries and reattempting the CREATE TABLE or DROP TABLE query.
Edited by Narayanan Iyer