| Bug #55059 | dont_log_query parameter controls warnings and logging in mysql_rm_table_part2! | ||
|---|---|---|---|
| Submitted: | 7 Jul 2010 17:56 | ||
| Reporter: | Luis Soares | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: General | Severity: | S3 (Non-critical) |
| Version: | 5.1+ | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.062 sec. using MySQL 8.4.5-u4-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
© 2025, Oracle Corporation and/or its affiliates
Description: mysql_rm_table_part2 contains a parameter: dont_log_query, which is used for: dont_log_query Don't write query to log files. This will also not generate warnings if the handler files doesn't exists As it states, this variable is used to control both warning generation in ha_delete_table and logging. This is a bit ambiguous and should be sorted out. For instance, if the binary log is closed, we could just set this variable to mysql_bin_log.is_open(), but given that it also controls warnings in ha_delete_table, we would be messing up with the warnings as well. How to repeat: Just inspect the code, for example in: tree: mysql-5.1-bugteam revid: davi.arnaut@sun.com-20100705120039-hyv00fc5ktsvr3zh Suggested fix: .