CALL
CREATE TABLE AS
INSERT INTO SELECT *
is supported.CREATE TABLE LIKE
DO
DELETE
DELETE
statement.HANDLER
IMPORT TABLE
dolt table import
INSERT
ON DUPLICATE KEY
clauses.LOAD DATA
LOAD XML
dolt table import
REPLACE
SELECT
UNION
and JOIN
, are supported.SELECT FROM AS OF
SELECT FOR UPDATE
SUBQUERIES
TABLE
SELECT * FROM TABLE
without a WHERE
clause.TRUNCATE
UPDATE
UPDATE
statement.VALUES
WITH
ADD COLUMN
ADD CHECK
ADD CONSTRAINT
ADD FOREIGN KEY
ADD PARTITION
ALTER COLUMN
ALTER DATABASE
ALTER INDEX
ALTER PRIMARY KEY
ALTER TABLE
ALTER TABLE
statements are supported. See the rest of this table for details.ALTER TYPE
ALTER VIEW
CHANGE COLUMN
CREATE DATABASE
CREATE EVENT
CREATE FUNCTION
CREATE INDEX
CREATE SCHEMA
CREATE TABLE
CREATE TABLE AS
COMMIT
statement atomically updates the working set for the connected headDOLT_COMMIT
function, currently violate ACID properties in a high concurrency environment. For safety, we recommend using the Dolt commit layer in a single-threaded fashion, or offline, and limiting SQL statements to the SQL transaction layer when multiple clients per HEAD are required.BEGIN
START TRANSACTION
COMMIT
DOLT_COMMIT()
DOLT_COMMIT()
commits the current SQL transaction, then creates a new Dolt commit on the current HEAD with the contents. See docs on DOLT_COMMIT() for details.LOCK TABLES
LOCK TABLES
parses correctly but does not prevent access to those tables from other sessions.ROLLBACK
SAVEPOINT
RELEASE SAVEPOINT
ROLLBACK TO SAVEPOINT
@@autocommit
SET TRANSACTION
START TRANSACTION
UNLOCK TABLES
UNLOCK TABLES
parses correctly, but since LOCK TABLES
doesn't prevent concurrent access it's essentially a no-op.PREPARE
EXECUTE
ALTER USER
CREATE ROLE
CREATE USER
DROP ROLE
DROP USER
GRANT
RENAME USER
REVOKE
SET DEFAULT ROLE
SET PASSWORD
SET ROLE
SET
SET CHARACTER SET
SET NAMES
KILL QUERY
EXPLAIN
USE