MySQL Bugs: #37524: enable profiling doesn't work without enable community features

Bug #37524	enable profiling doesn't work without enable community features
Submitted:	19 Jun 2008 12:40	Modified:	29 Jul 2008 21:53
Reporter:	Susanne Ebrecht	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Errors	Severity:	S3 (Non-critical)
Version:	5.1	OS:	Any
Assigned to:	Marc ALFF	CPU Architecture:	Any

Description:
$ ./configure --enable-profiling

Here you will get:
SHOW PROFILE should be enabled.... no, overridden by community-features disabled

$ ./configure --enable-community-features --enable-profiling

This will work.

The bug here in my eyes is that there should be an automatism and --enable-profiling should implicate --enable-community-features.

Means when you say: --enable-profile then it should be automatically --enable-community-features plus --enable-profile.

How to repeat:
see above

Suggested fix:
dependency fix

Both --enable-community-features and --enable-profiling are necessary at configuration time to enable statement profiling. I have updated the manual to reflect this requirement.

However, the error message produced by the server is incorrect:

mysql> show profile;
ERROR 1289 (HY000): The 'SHOW PROFILE' feature is disabled; you need MySQL built with 'enable-profiling' to have it working

The error message should state that both --enable-community-features and --enable-profiling are required, not just --enable-profiling.

The error message:

mysql> show profile;
ERROR 1289 (HY000): The 'SHOW PROFILE' feature is disabled; you need MySQL built with
'enable-profiling' to have it working

is correct: show profile requires --enable-profiling.

Now, it is correct that there is a usability issue here,
since --enable-profiling requires --enable-community-features,
and building with --enable-profiling alone appear to succeed but has no effect.

However, this should be fixed in the configure.in file, not in the error
message in the server code.
See related Bug#38359, which was reported for the issue in ./configure.

Closing this report as "not a bug", the error ER_FEATURE_DISABLED prints the
expected result.