In mysql-5.5, we are on 5.5.46 in Precise and Trusty and this was fixed
in upstream release 5.5.41.
In mysql-5.6, we are on 5.6.27 in Trusty, Vivid, Wily and Xenial and
this was fixed in upstream release 5.6.22.
** Changed in: mysql-5.5 (Ubuntu Precise)
Status: Triaged => Fix Released
**
Circling back:
upsteam bug #67433 has been closed. The unsafe syntax will be removed
in 5.5.41/5.6.22 (not yet released).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1357003
Won't Fix for mysql-5.5 in Utopic, since it is slated for removal in
favour of mysql-5.6 this cycle.
** Changed in: mysql-5.5 (Ubuntu)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in
Subscribing ~ubuntu-sru for a pre-upload (and pre-upstream-commit)
review.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1357003
Title:
SET GLOBAL sql_log_bin causes data loss
[http://blog.jcole.us/2014/08/08/stupid-and-dangerous-set-global-sql_log_bin/]
suggests that there is no known use case for this command, that the only
use of the command is by mistake, causes problems and/or data loss, and
this has happened in the real world in production environments.
If
** Bug watch added: MySQL Bug System #67433
http://bugs.mysql.com/bug.php?id=67433
** Also affects: mysql-server via
http://bugs.mysql.com/bug.php?id=67433
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team,
