Bug #178 USER() is badly replicated (is replicated to "")
Submitted: 21 Mar 2003 13:12 Modified: 21 Jul 2003 3:05
Reporter: Guilhem Bichot Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.0 OS:Any (all)
Assigned to: Assigned Account CPU Architecture:Any

[21 Mar 2003 13:12] Guilhem Bichot
see below

How to repeat:
start the master and slave (START SLAVE) and do

MASTER> create table u (a varchar(200));
Query OK, 0 rows affected (0.07 sec)

MASTER> insert into u values(user());
Query OK, 1 row affected (0.17 sec)

Immediately the slave server dies.

Suggested fix:
will look at it
[22 Mar 2003 6:38] Guilhem Bichot
Now I have fixed it to avoid SEGV (changeset 1.1688).
USER() is now replicated to "". Which is still a bug but a smaller one, the same way CONNECTION_ID() is badly replicated.
[22 Apr 2003 4:39] Guilhem Bichot
Not urgent, see bug #177 for ideas on how to fix it one day.
[26 Apr 2003 7:07] Michael Widenius
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments
to the original bug instead.

Thank you for your interest in MySQL.

Same as bug #177