Bug #7631 NDB$EVENT contains unreadable event and table names
Submitted: 3 Jan 2005 14:08 Modified: 7 Jan 2005 23:02
Reporter: Johan Andersson Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:* OS:Any (*)
Assigned to: Tomas Ulin CPU Architecture:Any

[3 Jan 2005 14:08] Johan Andersson 
Description:
Correct table and event names are not printed:

ndb_select_all -d sys 'NDB$EVENTS_0'
NAME      EVENT_TYPE      TABLE_NAME      ATTRIBUTE_MASK  SUBID   SUBKEY
[16 128 times]  7                 [16 128 times]        [2 0 0 0]                     260        131332
[16 128 times]  7                 [16 128 times]        [7 0 0 0]                     23         131095
[16 128 times]  7                [16 128 times]         [7 0 0 0]                     28         131100
[16 128 times]  7                [16 128 times]         [2 0 0 0]                     257       131329
[16 128 times]  7                [16 128 times]         [6 0 0 0]                     181       131253
5 rows returned.

How to repeat:

Run ndbapi_example5 without dropping the event and do:

ndb_select_all -d sys 'NDB$EVENTS_0'
[3 Jan 2005 14:08] Johan Andersson 
updated a field...
[3 Jan 2005 14:32] Johan Andersson 
changed title
[6 Jan 2005 10:02] Tomas Ulin 
Problem is poor printout routine in ndb_select_all
[6 Jan 2005 13:49] Jonas Oreland 
I think I think that we should abandom NDB$EVENT totally
[7 Jan 2005 23:02] Tomas Ulin 
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