phpMyAdmin can lint SQL in the browser before the database server sees it. If a valid named CHECK constraint is underlined as a syntax error, test the exact statement against the target MySQL or MariaDB server before rewriting valid SQL.
Last updated: November 8, 2026.
CREATE TABLE sequence_state (
id INT UNSIGNED NOT NULL PRIMARY KEY,
next_value INT UNSIGNED NOT NULL DEFAULT 1,
CONSTRAINT chk_next_value CHECK (next_value >= 1)
);
SHOW CREATE TABLE sequence_state;
SELECT CONSTRAINT_NAME, CHECK_CLAUSE
FROM INFORMATION_SCHEMA.CHECK_CONSTRAINTS
WHERE CONSTRAINT_SCHEMA = DATABASE();Run the statement in a disposable schema using the MySQL or MariaDB command-line client. If the server creates the table and reports the constraint, the phpMyAdmin warning is a client-side parser problem rather than a database syntax error.
Check the server and client separately
MySQL’s CHECK constraint reference permits CONSTRAINT symbol CHECK (expr) and documents the expressions that are allowed. Confirm the exact server product and version because MariaDB and MySQL do not share every parser rule or feature version.
phpMyAdmin’s configuration reference says $cfg['LintEnable'] controls whether its parser finds errors before execution. Lint feedback is useful, but it is not the database server’s final decision.
Use a narrow workaround
Update phpMyAdmin to a release containing the relevant parser fix. Until then, an administrator can disable linting in config.inc.php with $cfg['LintEnable'] = false; or execute the migration through a trusted database client. This changes editor validation only; it does not bypass server permissions or constraint enforcement.
Do not remove a working constraint merely to silence the editor. Test an insert that violates the condition and confirm the server rejects it. Then use SHOW CREATE TABLE to preserve the server’s canonical definition in migration evidence.
When reporting the parser problem, include the minimal SQL statement, phpMyAdmin version, database product and version, and whether the server accepted it. Avoid attaching a full production dump. A small reproducer lets maintainers distinguish a lexer regression from version-specific SQL that the server itself rejects.
Continue with phpMyAdmin configuration, MySQL upgrade checks, and MySQL schema-error troubleshooting.
