An error occurred fetching the project authors.
- 04 Jan, 2006 1 commit
-
-
knielsen@mysql.com authored
the bug is fixed.
-
- 22 Dec, 2005 1 commit
-
-
lars@mysql.com authored
This includes both code and test cases.
-
- 17 Nov, 2005 1 commit
-
-
konstantin@mysql.com authored
function with a cursor". Enable execution of SELECT queries in SP on slave.
-
- 10 Nov, 2005 1 commit
-
-
guilhem@mysql.com authored
Indeed now that stored procedures CALL is not binlogged, but instead the invoked substatements are, the restrictions applied by log-bin-trust-routine-creators=0 are superfluous for procedures. They still need to apply to functions where function calls are written to the binlog (for example as "DO myfunc(3)"). We rename the variable to log-bin-trust-function-creators but allow the old name until some future version (and issue a warning if old name is used).
-
- 12 Oct, 2005 1 commit
-
-
dlenev@mysql.com authored
can't be executed on slave". It will be possible to solve this problem in more correct way when we will implement WL#2897 "Complete definer support in the stored routines".
-
- 01 Sep, 2005 1 commit
-
-
msvensson@neptunus.(none) authored
-
- 25 Aug, 2005 1 commit
-
-
sergefp@mysql.com authored
"Interleaved SPs execution is now binlogged properly, "SELECT spfunc()" is binlogged too. The known remaining issue is binlogging/replication of "a routine is deleted while it is executed" scenario.
-
- 19 Jul, 2005 1 commit
-
-
dlenev@mysql.com authored
"Triggers have the wrong namespace" "Triggers: duplicate names allowed" "Triggers: CREATE TRIGGER does not accept fully qualified names" "SHOW TRIGGERS"
-
- 06 May, 2005 1 commit
-
-
gbichot@quadita2.mysql.com authored
writing DROP and CREATE TRIGGER to binlog, disabling binlogging of substatements, testing.
-
- 05 May, 2005 2 commits
-
-
gbichot@quadita2.mysql.com authored
-
gbichot@quadita2.mysql.com authored
Approximative fixes for BUG#2610,2611,9100 i.e. WL#2146 binlogging/replication of routines (stored procs and functions). Approximative, because it's using our binlogging way (what we call "query"-level) and this is not as good as record-level binlog (5.1) would be. It imposes several limitations to routines, and has caveats (which I'll document, and for which the server will try to issue errors but that is not always possible). Reason I don't propagate caller info to the binlog as planned is that on master and slave users may be different; even with that some caveats would remain.
-