You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ebac6f9
Browse filesBrowse the repository at this point in the historyBrowse files
feat: parse MySQL LOCK TABLES, UNLOCK TABLES and the backup lock statements
mysqldump wraps the rows of each table in LOCK TABLES ... WRITE and
UNLOCK TABLES, so a dump script failed at its first table. LOCK
INSTANCE FOR BACKUP and UNLOCK INSTANCE failed as well.
LOCK TABLES extends LockStatement: each target keeps its lock type
(TableLockType) and its table keeps the alias, and isTablesKeyword()
records the TABLES spelling. PostgreSQL and Oracle LOCK keep their
reading, since neither follows a table name with an alias or a lock
type. MariaDB's WRITE CONCURRENT is a lock type, and its WAIT and
NOWAIT reuse the wait clause of the statement. UNLOCK TABLES and the
backup lock name no table, so they are the new UnlockStatement and
BackupLockStatement. UNLOCK becomes a non-reserved keyword and remains
usable as a name.
Signed-off-by: minleejae <mmj9808@gmail.com>
0 commit comments