v0.13.0

Schemaic v0.13.0 — CHECK constraints, triggers and PostgreSQL's enums, domains and sequences in the schema editor, plus a pre-release review that hardened all of it.

Highlights

• Triggers, on both engines. A table's whole trigger set is edited in one modal — drop one, change another, add a third, applied as a single plan. On PostgreSQL a trigger calls a function rather than carrying a body, so there's an editor for those beside it.
• CHECK constraints join columns, indexes and foreign keys in the table designer, on MySQL, MariaDB and PostgreSQL.
• PostgreSQL enums, domains and sequences are browsable in the schema tree and fully editable — including the drop-and-rebuild PostgreSQL forces when an enum value is removed or reordered, which the preview names before you apply it.

Improvements

• MySQL and MariaDB are told apart where they genuinely diverge instead of being treated as one server — so the designer stops offering MariaDB an "Enforced" switch it has no syntax for.
• Every modal wears the same layout and buttons. Captions, sections, footers and hint lines come from one place instead of three.
• "Open in editor" hands over a script that runs. A MySQL trigger body's own semicolons used to split it into fragments in the query tab.
• A view's triggers are reachable on PostgreSQL, which is where INSTEAD OF lives.

Fixes

• A MariaDB column's CHECK survives an edit to that column. Widening qty INT CHECK (qty > 0) silently deleted the constraint, and the next -5 was accepted. Removing or editing such a constraint failed outright.
• Escape closes a modal again while a text field is focused, and a popup opened over one no longer leaves it keyboard-dead.
• Clicking the padding of a text field focuses it instead of doing nothing.
• Clicking inside an already-focused field no longer commits it.
• Table and view icons in the schema tree follow a live theme switch instead of keeping the old theme's colour.