Define DDL (Data Definition Language)

[vgapeyev]

A few of the aspects to consider, specific to PartiQL (compared to SQL):

• Should DDL be coupled with DML/updatability, or could/should there be a pure "data description" component?
• Nested data.
• Schemaless data.
• Open/closed schemas (such as a possibility for more attributes in the stored data than is described in its schema.)
• Support for SQL-compatible DDL -- needed or not?

[This list is expected to grow as we understand the matter.]

[yliuuuu]

From a perspective of SQL conformance:

Qualified Table Name

Currently, in the kotlin-implementation. DDL does not support namespace in table name, meaning we can do only CREATE TABLE myTable .... but not CREATE TABLE myCatalog.mySchema.myTable.

We should support variable length namespace when defining DDL, but the definition of what SQL called catalog, schema, should be its own project.

Constraint

Currently, the kotlin implementation support parsing of column constraint (with constraint name):

1. NOT NULL: The SQL equivalent of declaring a non-null constraint.
2. NULL: I don't have much context on why this constraint is needed.

Potentially, we need to explore the possibility of adding:

• Additional "column" constraint:
  • Unique/ Primary Key
  • Reference/ Match
  • Check

Additional Parts

• Additional "column declaration" part:
  • Default clause
  • Collate clause
  • Additional part in "Create Table" statement:
  • Global vs Local
  • Temporary vs persistent Table.
  • ON COMMIT Clause.