Gleb Paharenko wrote:
Hello.
This should be interesting for you:
http://bugs.mysql.com/bug.php?id=16266
Hi,
The bug report implies that if you recreate the triggers on the slave
(deleting them manually from the database directory), then it resolves
the issue. Unfortunately, the proble
Hello.
This should be interesting for you:
http://bugs.mysql.com/bug.php?id=16266
Ian Sales (DBA) wrote:
> - unfortunately, the set up demands that the master stays at 4.0. I
> can't change that. The triggers were working in 5.0.16. It's the new
> DEFINER that was added with 5.0.17
Hello.
> I've subsequently upgraded the instance to 5.0.18,
Have you updated master to 5.0.18 as well?
Ian Sales (DBA) wrote:
>
> After upgrading to 5.0.17, the triggers on one of my instances now break
> replication with a "definer is not fully qualified" error. I set the
> DEFIN
Gleb Paharenko wrote:
Hello.
I've subsequently upgraded the instance to 5.0.18,
Have you updated master to 5.0.18 as well?
- unfortunately, the set up demands that the master stays at 4.0. I
can't change that. The triggers were working in 5.0.16. It's the new
DEFINER that w
After upgrading to 5.0.17, the triggers on one of my instances now break
replication with a "definer is not fully qualified" error. I set the
DEFINER in the CREATE TRIGGER statement to CURRENT_USER (i.e.,
[EMAIL PROTECTED]), but the error still occurs. If I try setting the
DEFINER to any othe
