Support Table CHECK Constraints

[forrest-akin]

Currently, there's no way to specify table CHECK constraints in TableCreateStatements. Adding an .extra() method similar to ColumnDef would probably be the easiest way to add support for this.

[billy1624]

You can specify unique, primary key and reference constraints with index, primary_key and foreign_key methods in TableCreateStatement.

[billy1624]

However, yesterday I discovered the generated unique constraint SQL statement for Postgres is incorrect. There will be an excess "KEY" keyword in the statement. #85

    Table::create()
        .table(Alias::new("film"))
        .col(ColumnDef::new(Alias::new("title")).char_len(255).not_null())
        .col(ColumnDef::new(Alias::new("description")).text())
        .primary_key(Index::create().primary().col(Alias::new("film_id")))
        .index(Index::create().unique().col(Alias::new("title")))
        .to_owned()

[billy1624]

You can checkout this example, https://github.com/SeaQL/sea-schema/blob/e284b5b72c098f3afab5600f848245fa28127927/tests/live/postgres/src/main.rs#L75-L162.

[forrest-akin]

Oops, I meant to specify table CHECK constraints is what's missing. I did run into the unique key issue, but I think the rest is fine as you mentioned.

[billy1624]

Hey @forrest-akin, sorry for the delay. I've just open a tracking issue for this feature request :D

• Support Table CHECK Constraints #397

[diptanu]

Hi is this feature not released? I see the issue linked above and the PRs are done but don't have it on the latest crate.