1630
MariaDBWARNINGCriticalSyntaxHIGH confidence
Deprecated syntax used with no replacement available
Production Risk
Low now, High in future — code will break when the feature is removed.
What this means
A deprecated SQL syntax or feature was used and there is no direct replacement. The feature will be removed in a future MySQL version.
Why it happens
- 1Using SQL constructs or options that are deprecated and scheduled for removal.
- 2Old application code has not been updated to use current syntax.
How to reproduce
trigger — this will error
trigger — this will error
-- Example: using deprecated TYPE= instead of ENGINE= CREATE TABLE t (id INT) TYPE=InnoDB;
expected output
Warning 1630: Deprecated syntax: TYPE= is deprecated, use ENGINE= instead.
Fix
Update to current syntax
Update to current syntax
CREATE TABLE t (id INT) ENGINE=InnoDB;
Why this works
Using the current supported syntax removes the deprecation warning.
What not to do
✕
Sources
Official documentation ↗
MySQL 8.0 — 1630 ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT
Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev