ER_YES is an internal MySQL note code that appears in SHOW WARNINGS output after statements like EXPLAIN FORMAT=JSON and signals an informational message, not a failure.
MySQL Error 1003: ER_YES appears as a YES note in SHOW WARNINGS after extended EXPLAIN or optimizer traces. It is informational and indicates MySQL generated a note, not a failure. Review SHOW WARNINGS for real issues or suppress the note with proper SQL session settings.
YES
MySQL assigns the symbolic name ER_YES to error code 1003. Instead of signaling a failure, the server uses this placeholder when it needs to store a simple YES value in the Code column of Warning or Note rows.
The note usually appears after diagnostic statements such as EXPLAIN FORMAT=JSON, OPTIMIZER_TRACE, or ANALYZE TABLE.
When you immediately run SHOW WARNINGS, rows with Level = 'Note' and Code = 1003 display the literal word YES.
This output can surprise developers who expect only errors or warnings. Because ER_YES is not an error state, queries still succeed. Understanding why the note is generated helps you separate harmless information from actionable problems.
No application logic must change solely because ER_YES appears. The note is informational.
You only need to investigate if other Warning or Error rows accompany it.
MySQL documents ER_YES in the MySQL Source and in the server error-const file, describing it as “Used in the construction of other messages.” Public manuals reference it indirectly through SHOW WARNINGS examples.
.
No. It is an informational note that does not affect query execution.
You cannot disable the code directly, but you can avoid statements that generate it or filter Level = 'Note' in SHOW WARNINGS.
No. It merely records a YES value in diagnostic output. It never signals corruption or data loss.
Galaxy collapses ER_YES notes by default and surfaces actionable warnings, letting developers focus on genuine problems.
.avif)
.avif){kind=logo}
