summaryrefslogtreecommitdiff
path: root/sql/log_event.h
Commit message (Collapse)AuthorAgeFilesLines
* Fixes during review of pushed codemonty@mysql.com2005-10-271-3/+2
| | | | Added back missing return in mysql_delete()
* Merge mysql.com:/users/lthalmann/bkroot/mysql-5.0lars@mysql.com2005-10-251-12/+23
|\ | | | | | | into mysql.com:/users/lthalmann/bk/mysql-5.0-enum-logtype
| * Fixed enum numbering, patch 2lars@mysql.com2005-10-241-11/+21
| |
| * Reducing risk for incorrect merges. Since we are multiple teams working on lars@mysql.com2005-10-241-9/+10
| | | | | | | | | | | | | | different features, adding numbering to enums reduce the risk that code will be merged incorrectly. This particular enum must have fixed values to ensure that an upgraded server always can read old logs. I added this, since I noticed the incorrect order in the RBR clone.
* | Merge mysql.com:/users/lthalmann/bkroot/mysql-5.0lars@mysql.com2005-10-191-32/+48
|\ \ | |/ |/| | | into mysql.com:/users/lthalmann/bk/mysql-5.0-hexdump
| * mysqlbinlog --hexdump patch 4:lars@mysql.com2005-10-191-34/+39
| | | | | | | | Rename last_event_info to print_event_info to better reflect the new semantics
| * mysqlbin --hexdump patch 3lars@mysql.com2005-10-121-49/+39
| |
| * mysqlbinlog --hexdump additional patch 2lars@mysql.com2005-09-301-23/+23
| | | | | | | | | | - Fixes related to Guilhems review - Special printing of event header
| * mysqlbinlog --hexdump augments each log entry with byte informationlars@mysql.com2005-09-291-24/+45
| |
* | fixes after merge of 4.1.guilhem@mysql.com2005-10-131-16/+0
| |
* | Merge mysql.com:/home/mysql_src/mysql-4.1guilhem@mysql.com2005-10-121-9/+24
|\ \ | |/ |/| | | | | into mysql.com:/home/mysql_src/mysql-5.0; a very bad automerge (issues with non-ascii chars), plus some hard conflicts I'll fix by hand in a next cset
| * Fix for BUG#13023: "SQL Thread is up but doesn't move forward". Details in ↵guilhem@mysql.com2005-10-121-10/+18
| | | | | | | | | | | | | | | | | | | | slave.cc; in short we now record whenever the slave I/O thread ignores a master's event because of its server id, and use this info in the slave SQL thread to advance Exec_master_log_pos. Because if we do not, this variable stays at the position of the last executed event, i.e. the last *non-ignored* executed one, which may not be the last of the master's binlog (and so the slave *looks* behind the master though it's data-wise it's not).
* | Implement WL#2661 "Prepared Statements: Dynamic SQL in Stored Procedures".konstantin@mysql.com2005-09-031-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The idea of the patch is to separate statement processing logic, such as parsing, validation of the parsed tree, execution and cleanup, from global query processing logic, such as logging, resetting priorities of a thread, resetting stored procedure cache, resetting thread count of errors and warnings. This makes PREPARE and EXECUTE behave similarly to the rest of SQL statements and allows their use in stored procedures. This patch contains a change in behaviour: until recently for each SQL prepared statement command, 2 queries were written to the general log, e.g. [Query] prepare stmt from @stmt_text; [Prepare] select * from t1 <-- contents of @stmt_text The chagne was necessary to prevent [Prepare] commands from being written to the general log when executing a stored procedure with Dynamic SQL. We should consider whether the old behavior is preferrable and probably restore it. This patch refixes Bug#7115, Bug#10975 (partially), Bug#10605 (various bugs in Dynamic SQL reported before it was disabled).
* | Merge mysql.com:/home/emurphy/src/bk-clean/mysql-4.1elliot@mysql.com2005-08-191-1/+1
|\ \ | |/ | | | | into mysql.com:/home/emurphy/src/work/mysql-5.0
| * Bug#11338 Fixes from review (identical functionality).elliot@mysql.com2005-08-191-1/+1
| |
* | log_event.h:serg@serg.mylan2005-08-061-0/+4
| | | | | | | | extra safety for OPTIONS_WRITTEN_TO_BIN_LOG
* | Name resolution context added (BUG#6443)bell@sanja.is.com.ua2005-07-011-1/+2
| |
* | Merge from 4.1msvensson@neptunus.(none)2005-05-261-1/+1
|\ \ | |/
| * Add ifdefs to control when "#pragma implementation" should be usedmsvensson@neptunus.(none)2005-05-261-1/+1
| | | | | | | | Added some more ifdefs for "#pragma interface"
* | Approximative fixes for BUG#2610,2611,9100 i.e. WL#2146 ↵gbichot@quadita2.mysql.com2005-05-051-3/+2
| | | | | | | | | | | | | | | | | | 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.
* | Enabled more tests of STR_TO_DATE()monty@mysql.com2005-03-301-1/+1
| | | | | | | | Fixed that datetime gives warning for zero dates in traditional mode
* | Give warnings if wrong date/time/datetime argument for STR_TO_DATEmonty@mysql.com2005-03-301-0/+2
| | | | | | | | | | Small fixes while doing review of new pushed code More test cases for decimal
* | WWe now store the catalog in Query_log_event in binlog WITHOUT its end zero.gbichot@quadita2.mysql.com2005-03-251-2/+14
| | | | | | | | | | | | | | | | | | | | | | | | This saves one byte per Query_log_event on disk compared to 5.0.[0..3]. Compatibility problems with 5.0.x where x<4 are explained in the comments in log_event.cc. Putting back s/my_open(O_TRUNC)/(my_delete+my_create) change which had been wiped away by somebody doing a wrong 4.1->5.0 merge (which happened just before 5.0.3 :( ). Applying it to new events for LOAD DATA INFILE. If slave fails in Execute_load_query_log_event::exec_event(), don't delete the file (so that it's re-usable at next START SLAVE). And (youpi!) fix for BUG#3247 "a partially completed LOAD DATA INFILE is not executed at all on the slave" (storing an Execute_load_query_log_event to binlog, with its error code, instead of Delete_file_log_event).
* | Last part of WL#1062: better replication of timezones: no more usegbichot@production.mysql.com2005-03-221-5/+40
| | | | | | | | | | of SET ONE_SHOT; storing tz info directly in event (if this info is needed), it's now allowed to have different global tz on master and slave.
* | WL#874 "Extended LOAD DATA". dlenev@brandersnatch.localdomain2005-03-161-5/+121
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Now one can use user variables as target for data loaded from file (besides table's columns). Also LOAD DATA got new SET-clause in which one can specify values for table columns as expressions. For example the following is possible: LOAD DATA INFILE 'words.dat' INTO TABLE t1 (a, @b) SET c = @b + 1; This patch also implements new way of replicating LOAD DATA. Now we do it similarly to other queries. We store LOAD DATA query in new Execute_load_query event (which is last in the sequence of events representing LOAD DATA). When we are executing this event we simply rewrite part of query which holds name of file (we use name of temporary file) and then execute it as usual query. In the beggining of this sequence we use Begin_load_query event which is almost identical to Append_file event
* | don't log BEGIN in auto-commit modeserg@serg.mylan2005-02-231-1/+1
| | | | | | | | correct end_log_pos for Xid_log_event
* | post-review fixes. Now ROLLBACK is done in Format_description_log_eventserg@serg.mylan2005-02-171-20/+10
| |
* | manually mergedserg@serg.mylan2005-02-141-38/+108
|\ \
| * | auto-ROLLBACK if binlog was not closed properlyserg@serg.mylan2005-02-091-24/+49
| | | | | | | | | | | | auto-commit on Xid_log_event
| * | query_id and my_xid -> ulonglongserg@serg.mylan2005-01-271-7/+16
| | | | | | | | | | | | | | | fix for binlog+autocommit+tclog comments, style fixes
| * | XA (not completely polished out yet)serg@serg.mylan2005-01-161-25/+61
| | |
* | | WL#1062 "log charset info into all Query_log_event":guilhem@mysql.com2005-02-031-4/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | we store 7 bytes (1 + 2*3) in every Query_log_event. In the future if users want binlog optimized for small size and less safe, we could add --binlog-no-charset (and binlog-no-sql-mode etc): charset info is something by design optional (even if for now we don't offer possibility to disable it): it's not a binlog format change. We try to reduce the number of get_charset() calls in the slave SQL thread to a minimum by caching the charset read from the previous event (which will often be equal to the one of the current event). We don't use SET ONE_SHOT for charset-aware repl (we still do for timezones, will be fixed later). No more errors if one changes the global value of charset vars on master or slave (as we log charset info in all Query_log_event). Not fixing Load_log_event as it will be rewritten soon by Dmitri. Testing how mysqlbinlog behaves in rpl_charset.test. mysqlbinlog needs to know where charset file is (to be able to convert a charset number found in binlog (e.g. in User_var_log_event) to a charset name); mysql-test-run needs to pass the correct value for this option to mysqlbinlog. Many result udpates (adding charset info into every event shifts log_pos in SHOW BINLOG EVENTS). Roughly the same job is to be done for timezones :)
* | | Merge with 4.1 tree to get fix for INSERT IGNORE ... ON DUPLICATE KEYmonty@mysql.com2005-01-031-2/+2
|\ \ \ | |/ / |/| / | |/
| * Remove DUP_IGNORE from enum_duplicates and instead use a separate ignore flagmonty@mysql.com2004-12-311-2/+2
| | | | | | | | This allows use to use INSERT IGNORE ... ON DUPLICATE ...
* | Merge with 4.1monty@mysql.com2004-12-061-3/+17
|\ \ | |/
| * Bug#6391 (binlog-do-db rules ignored)mats@mysql.com2004-12-031-3/+17
| | | | | | | | | | | | | | CREATE DATABASE statement used the current database instead of the database created when checking conditions for replication. CREATE/DROP/ALTER DATABASE statements are now replicated based on the manipulated database.
* | Mergeguilhem@mysql.com2004-11-161-1/+1
|\ \ | |/
| * BUG#6353 V2:lars@mysql.com2004-11-151-1/+1
| | | | | | | | | | | | Replication using replicate-rewrite-db did not work for LOAD DATA INFILE. Now is does. There was one place in the code that used current database instead of the rewrite database.
* | merge with 4.1monty@mysql.com2004-10-291-1/+1
|\ \ | |/
| * true,false -> TRUE, FALSEmonty@mishka.local2004-10-141-1/+1
| | | | | | | | Simple fixes/optimization of things discovered during review of new pushed code
* | Added options --auto-increment-increment and --auto-increment-offset.monty@mishka.local2004-09-151-125/+131
| | | | | | | | | | | | | | | | | | | | This allows one to setup a master <-> master replication with non conflicting auto-increment series. Cleaned up binary log code to make it easyer to add new state variables. Added simpler 'upper level' logic for artificial events (events that should not cause cleanups on slave). Simplified binary log handling. Changed how auto_increment works together with to SET INSERT_ID=# to make it more predictable: Now the inserted rows in a multi-row statement are set independent of the existing rows in the table. (Before only InnoDB did this correctly)
* | Replication: various small fixes specific to the new binlog format of 5.0guilhem@mysql.com2004-07-261-1/+1
| | | | | | | | (including one which may explain autobuild's failure of yesterday)
* | misc fixes for compile-time errorsserg@serg.mylan2004-07-211-104/+104
| |
* | Merge 4.1 -> 5.0.pem@mysql.com2004-04-071-2/+8
|\ \ | |/
| * Merge with 4.0 to get fix for mysqlbinlogmonty@mysql.com2004-02-161-1/+5
| |\
| | * Always use libtool with "--preserve-dup-deps" monty@mysql.com2004-02-131-1/+5
| | | | | | | | | | | | | | | Always use all LOAD DATA options in replication. Fixed problem in mysqlbinlog where LOAD DATA options could be overwritten.
| * | Merge with 4.0.18monty@mysql.com2004-02-111-1/+3
| |\ \ | | |/
| | * fixed bug #1378 "mysqlbinlog for remote host is broken"vva@eagle.mysql.r18.ru2004-02-061-1/+3
| | |
* | | Update for VC++monty@mysql.com2003-12-211-3/+3
| | | | | | | | | | | | (Fixed project files, compiler warnings etc..)
* | | Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-5.0guilhem@mysql.com2003-12-191-2/+2
|\ \ \ | |/ / | | | | | | into mysql.com:/home/mysql_src/mysql-5.0-new-binlog-format
View Lorry Controller Status