Bug #72062 MySQL 5.7 CONFLICTS with MariaDB w/r/t 1900+ range for error codes
Submitted: 17 Mar 2014 16:13 Modified: 17 Mar 2014 16:33
Reporter: Felipe Gasper (OCA) Email Updates:
Status: Analyzing Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:5.7 OS:Any
Assigned to: Assigned Account CPU Architecture:Any
Tags: error code

[17 Mar 2014 16:13] Felipe Gasper
Kristian Nielsen at MariaDB suggested that I file a bug here about a conflict between MySQL 5.7 and MariaDB’s production release with the 1900+ range for error codes.

If possible, this should be changed before MySQL 5.7 goes to GA to prevent conflicts in the error codes that would adversely affect implementers.


How to repeat:

Suggested fix:
Change the 1900+ error codes in MySQL 5.7 to use a different range. MariaDB should perhaps switch to a different range for its codes entirely, but as their implementation is already GA, the safer thing for both parties would seem to be for MySQL to make an accommodation here.
[21 Mar 2014 19:08] Peter Zaitsev
Whatever way this specific issue is resolved with MariaDB I would suggest what Oracle takes on itself to be the "registrar" or error code ranges which it can when issue to other MySQL variants to avoid conflicts 

MariaDB, Percona Server,  Amazon RDS, Google Cloud SQL,  HP Cloud etc all could potentially add error codes specific to their implementation and it would be best if we can ensure they do not overlap.