Bug #20463 ndb_X_error.log doesn't indicate commercial binary
Submitted: 14 Jun 2006 14:49 Modified: 3 Nov 2006 5:20
Reporter: Stewart Smith Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:4.1-> OS:
Assigned to: Stewart Smith CPU Architecture:Any

[14 Jun 2006 14:49] Stewart Smith 
Description:
Commercial source trees of MySQL server identify themselves as "MySQL Cluster Server (Commercial)".

However, in ndb_X_error.log, we just say "4.1.19" and not "4.1.19-commercial".

This is annoying as the license header in the sources is different, causing the jam() calls that produce the trace logs to have different line numbers from the bk tree. hard to then debug.

How to repeat:
play a trace log backwards and to a popular hollywood childens movie.

Suggested fix:
put "product name" in error log.
[3 Nov 2006 5:20] Stewart Smith 
5.1 does this correctly. no real point fiddling with 4.1 at this point in time.