MySQL Bugs: #15293: renamed ER_WARN_DATA_TRUNCATED did break API compatibility

Bug #15293	renamed ER_WARN_DATA_TRUNCATED did break API compatibility
Submitted:	28 Nov 2005 17:09	Modified:	5 Dec 2005 18:56
Reporter:	Domas Mituzas	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.0.17-BK, 5.0.16	OS:
Assigned to:	Paul DuBois	CPU Architecture:	Any

Description:
Changeset at http://lists.mysql.com/internals/20871 did change ER_WARN_DATA_TRUNCATED error constant into WARN_DATA_TRUNCATED, thus making it inconsistent and breaking clients who use this error code.

How to repeat:
include mysqld_error.h, WARN_DATA_TRUNCATED is there, not ER_WARN_DATA_TRUNCATED

Suggested fix:
provide consistent error messages with previous versions, as well as consistent naming in this version.

Thank you for a bug report. Verified on latest 5.0.17-BK sources also (ChangeSet@1.2013.1.1, 2005-11-26 20:23:20+01:00). 

That error code is even "documented" at http://dev.mysql.com/doc/refman/5.0/en/error-messages-server.html, but because this part of documentation is generated automatically, it is still a bug or a request to document and explain this change in some prominent place 9including the upgrade from 4.1 to 5.0 section!).

OK. Even if it was an intended and correct change, I think, it should be reflected in the documentation (at least, at http://dev.mysql.com/doc/refman/5.0/en/upgrading-from-4-1.html, as incompatible change). May be, this change should be also back ported to 4.1.x?

Noted in 5.0.3 changelog and upgrading-from-4.1 section.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/33047