MySQL Bugs: #10365: Cluster handler uses non-standard error codes

Bug #10365	Cluster handler uses non-standard error codes
Submitted:	4 May 2005 18:04	Modified:	7 Jul 2005 13:39
Reporter:	Hartmut Holzgraefe	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	4.1.11	OS:	n/a
Assigned to:	Magnus Blåudd	CPU Architecture:	Any

Description:
Function ndbcluster_discover() in ha_ndbcluster.cc returns 0 on success
and one of HA_ERR_NO_CONNECTION, 1, 2 or 3 in case of errors

mysql_error() can't resolve the hardcoded magic numbers and 
the perror utility will confuse them with operating system error codes
so returning "Operation not permitted", "No such file or directory" and
"No such process" for the error codes 1, 2 and 3 which is very missleading 
to say at least

How to repeat:
see ha_ndbcluster.cc code

Suggested fix:
define proper HA_ERR... entries and use them

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/25753

Pushed to 4.1.13 and 5.0.9

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented in 4.1.13 and 5.0.9 change histories; closed.