Supported Statements
Data manipulation statements
Statement
Supported
Notes and limitations
CALL✅
CREATE TABLE AS❌
INSERT INTO SELECT * is supported.CREATE TABLE LIKE✅
DO❌
DELETE✅
No support for referring to more than one table in a single
DELETE statement.HANDLER❌
IMPORT TABLE❌
Use
dolt table importINSERT✅
Including support for
ON DUPLICATE KEY clauses.LOAD DATA✅
LOAD XML❌
Use
dolt table importREPLACE✅
SELECT✅
Most select statements, including
UNION and JOIN, are supported.SELECT FROM AS OF✅
Selecting from a table as of any known revision or commit timestamp is supported.
SELECT FOR UPDATE❌
Row-level locks are not supported.
SUBQUERIES✅
Subqueries work, but must be given aliases. Some limitations apply.
TABLE❌
Equivalent to
SELECT * FROM TABLE without a WHERE clause.TRUNCATE✅
UPDATE✅
No support for referring to more than one table in a single
UPDATE statement.VALUES❌
WITH✅
Data definition statements
Statement
Supported
Notes and limitations
ADD COLUMN✅
ADD CHECK✅
ADD CONSTRAINT✅
ADD FOREIGN KEY✅
ADD PARTITION❌
ALTER COLUMN🟠
Name and order changes are supported. Some but not all type changes are supported.
ALTER DATABASE❌
ALTER INDEX❌
Indexes can be created and dropped, but not altered.
ALTER PRIMARY KEY✅
ALTER TABLE✅
Not all
ALTER TABLE statements are supported. See the rest of this table for details.ALTER TYPE🟠
Some type changes are supported but not all.
ALTER VIEW❌
Views can be created and dropped, but not altered.
CHANGE COLUMN✅
CREATE DATABASE✅
Creates a new dolt database rooted relative to the server directory
CREATE EVENT❌
CREATE FUNCTION❌
CREATE INDEX🟠
Fulltext and spatial indexes are not supported.
CREATE SCHEMA✅
Creates a new dolt database rooted relative to the server directory
CREATE TABLE✅
CREATE TABLE AS❌
Transactional statements
Dolt supports atomic transactions like other SQL databases. It's also possible for clients to connect to different heads, which means they will never see each other's edits until a merge between heads is performed. See Working with branches for more detail.
Dolt has two levels of persistence:
- 1.The SQL transaction layer, where a
COMMITstatement atomically updates the working set for the connected head - 2.The Dolt commit layer, where commits are added to the Dolt commit graph with an author, a parent commit, etc.
Merging these two layers is a work in progress, and some functionality, such as the
DOLT_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.Statement
Supported
Notes and limitations
BEGIN✅
Synonym for
START TRANSACTIONCOMMIT✅
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❌
Different isolation levels are not yet supported.
START TRANSACTION✅
UNLOCK TABLES🟠
UNLOCK TABLES parses correctly, but since LOCK TABLES doesn't prevent concurrent access it's essentially a no-op.Prepared statements
Statement
Supported
Notes and limitations
PREPARE🟠
Prepared statements work in the SQL server context using com_prepare. PREPARE in a query is not supported.
EXECUTE🟠
Prepared statements work in the SQL server context using com_prepare. EXCEUTE in a query is not supported.
Access management statements
Statement
Supported
Notes and limitations
ALTER USER❌
CREATE ROLE✅
CREATE USER🟠
Only supports basic user creation with an optional password
DROP ROLE✅
DROP USER✅
GRANT🟠
Only handles static privileges down to the table level
RENAME USER❌
REVOKE🟠
Only handles static privileges down to the table level
SET DEFAULT ROLE❌
SET PASSWORD❌
SET ROLE❌
Session management statements
Statement
Supported
Notes and limitations
SET✅
SET CHARACTER SET🟠
`SET CHARACTER SET` parses correctly, but Dolt supports only the `utf8mb4` collation
SET NAMES🟠
`SET NAMES` parses correctly, but Dolt supports only the `utf8mb4` collation for identifiers
KILL QUERY✅
Utility statements
Statement
Supported
Notes and limitations
EXPLAIN✅
USE✅
Last modified 3d ago
Export as PDF
Copy link
Edit on GitHub