[Sal-ami]

The constraint check in _parse_column_line_robust used str.startswith() against a tuple of keywords. startswith matches prefixes, so any column whose name merely began with one of the keywords got treated as a table constraint and dropped.

This table loses three columns silently:

CREATE TABLE t (
    id SERIAL PRIMARY KEY,
    unique_code VARCHAR(10),
    constraint_name VARCHAR(50),
    check_flag BOOLEAN
);

Parsing it returns only id. The Schema Designer draws the table with a third of its columns missing and shows no error, so it looks like the SQL only ever declared one column.

The keywords are now matched with a word boundary. PRIMARY KEY (a, b), UNIQUE (email) and CONSTRAINT chk_len CHECK (...) are still skipped, and prefixed column names parse as columns.

Two tests added:

• one covers the column names above and fails on the current code with unique_code and constraint_name missing from the result
• one pins down that table-level constraints are still skipped, so the fix cannot drift the other way

Verified locally with the four test files that do not need a live database:

pytest tests/test_schema_parser.py tests/test_schema_cache.py tests/test_settings.py tests/test_models.py
80 passed

black --check and flake8 are clean on both changed files. mypy reports no issues on schema_parser.py. I could not run the database backed tests because there is no PostgreSQL server on my machine at this time.

[Sal-ami]

no ai btw