Bug #46991 Improve messages for NDB errors 723 and 4225

• Submitted: 29 Aug 2009 9:13
• Modified: 2 Sep 2009 12:36
• Reporter: Jon Stephens
• Status: Won't fix
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S3 (Non-critical)
• Version: mysql-5.1-telco-6.2
• OS: Any
• Assigned to: Jon Stephens
• CPU Architecture: Any
• Tags: telco-6.2+

[29 Aug 2009 9:13] Jon Stephens

Description:
Summary: Some NDB error messages aren't very descriptive/helpful in running down cause of error.

From Jørgen emails:

code: 723, msg: No such table existed
=>
code: 723, msg: Table "%s" with engine "Ndb" doesn't exist

(Table name - so that I can see that I have written it correctly, engine - because that was my actual bug, but I went looking for spelling instead).

code 4225, msg: All primary keys defined, call setValue/getValue

on the setValue line with id.

I think "All primary keys already defined, call setValue/getValue on other attributes" would be better 

How to repeat:
Write code, hit these errors.

Suggested fix:
Improve the error messages as suggested.

[2 Sep 2009 12:01] Jon Stephens

It turns out there's currently no easy way to pass in a table name to an error as sugested by Jørgen. Not sure what to do about this in terms of this bug, other than tag it as FUTURE or WONTFIX.

[2 Sep 2009 12:36] Jon Stephens

After discussing with Jonas, I've decided to set this to "To be fixed later".

[13 Mar 2014 13:37] Omer Barnir

This bug is not scheduled to be fixed at this time.