An error occurred fetching the project authors.
- 06 Jan, 2006 1 commit
-
-
jimw@mysql.com authored
-
- 22 Dec, 2005 1 commit
-
-
lars@mysql.com authored
This includes both code and test cases.
-
- 02 Dec, 2005 1 commit
-
-
elliot@mysql.com authored
Now when rolling back a transaction on a blackhole table, the transaction will not be written to the binlog.
-
- 05 May, 2005 1 commit
-
-
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.
-
- 26 Apr, 2005 1 commit
-
-
gbichot@quadita2.mysql.com authored
no rows of the blackhold engine (for this engine to be a binlog propagator). NOTE: blackhole.test currently hangs in 5.0 BUG#10175 so I'll merge without running this test; the person who fixes the hang will correct the merged blackhole.result or ask me to).
-
- 25 Mar, 2005 2 commits
-
-
brian@zim.(none) authored
-
brian@zim.(none) authored
-
- 23 Mar, 2005 1 commit
-
-
brian@zim.(none) authored
Additional storage engine called "blackhole". Customer request, and for that matter a Zawodny request. With this you can alter table to a type of table that would never store data. Its a /dev/null for a database.
-