An error occurred fetching the project authors.
- 12 Jan, 2005 1 commit
-
-
guilhem@mysql.com authored
when printing SET @var in mysqlbinlog, backtick the collation (as BINARY is a reserved word)
-
- 06 Jan, 2005 1 commit
-
-
monty@mysql.com authored
Split TABLE to TABLE and TABLE_SHARE (TABLE_SHARE is still allocated as part of table, will be fixed soon) Created Field::make_field() and made Field_num::make_field() to call this Added 'TABLE_SHARE->db' that points to database name; Changed all usage of table_cache_key as database name to use this instead Changed field->table_name to point to pointer to alias. This allows us to change alias for a table by just updating one pointer. Renamed TABLE_SHARE->real_name to table_name Renamed TABLE->table_name to alias Renamed TABLE_LIST->real_name to table_name
-
- 04 Jan, 2005 1 commit
-
-
monty@mysql.com authored
Add support for warnings for prepare of prepared statements Fixed test to work with --ps-protocol Fixed some test results
-
- 31 Dec, 2004 1 commit
-
-
monty@mysql.com authored
This allows use to use INSERT IGNORE ... ON DUPLICATE ...
-
- 16 Dec, 2004 1 commit
-
-
guilhem@mysql.com authored
-
- 03 Dec, 2004 2 commits
-
-
guilhem@mysql.com authored
(exactly, for the bug in 4.1 reported in this bug report). We just make Load_log_event work like Query_log_event for temp tables.
-
mats@mysql.com authored
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.
-
- 18 Nov, 2004 2 commits
-
-
guilhem@mysql.com authored
post-conflict-merge fix (duplicate comment)
-
guilhem@mysql.com authored
When mysqlbinlog prints LOAD DATA INFILE, let it print the thread id. Some customer would have benefited much from this in his recovery. All this change does is adding one commented (#) line before the LOAD DATA command, so it is quite innocuous.
-
- 15 Nov, 2004 1 commit
-
-
lars@mysql.com authored
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.
-
- 12 Nov, 2004 2 commits
-
-
pem@mysql.comhem.se authored
-
brian@avenger.(none) authored
-
- 07 Nov, 2004 1 commit
-
-
monty@mysql.com authored
Now thd->mem_root is a pointer to thd->main_mem_root and THR_MALLOC is a pointer to thd->mem_root. This gives us the following benefits: - Allow us to easily detect if arena has already been swapped before (this fixes a bug in setup_conds() where arena was swaped twice in some cases) - Faster swaps of arenas (as we don't have to copy the whole MEM_ROOT) - We don't anymore have to call my_pthread_setspecific_ptr(THR_MALLOC,...) to change where memory is alloced. Now it's enough to set thd->mem_root
-
- 03 Nov, 2004 1 commit
-
-
monty@mysql.com authored
FOUND is not a reserved keyword anymore Added Item_field::set_no_const_sub() to be able to mark fields that can't be substituted Added 'simple_select' method to be able to quickly determinate if a select_result is a normal SELECT Note that the 5.0 tree is not yet up to date: Sanja will have to fix multi-update-locks for this merge to be complete
-
- 21 Oct, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 20 Oct, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 19 Oct, 2004 1 commit
-
-
guilhem@mysql.com authored
as we already have db_len in Log_event. Only if rewrite_db() changed the db we need a strlen (so we now do the strlen() in rewrite_db). Plus a test (we had none for --replicate-rewrite-db :( ).
-
- 24 Sep, 2004 1 commit
-
-
guilhem@mysql.com authored
In binary log events, flags are 2 bytes, not 4. Using 4 resulted in buffer overflow (and on a certain build it resulted in overwriting another part of the event without crashing :( ).
-
- 23 Sep, 2004 1 commit
-
-
guilhem@mysql.com authored
we do not increment rli->group_master_log_pos if we are just after a SET ONE_SHOT (it's not a standalone event)
-
- 15 Sep, 2004 1 commit
-
-
monty@mishka.local authored
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)
-
- 09 Sep, 2004 1 commit
-
-
monty@mysql.com authored
Fixed (together with Guilhem) bugs in mysqlbinlog regarding --offset Prefix addresses with 0x for easier comparisons of debug logs Fixed problem where MySQL choosed index-read even if there would be a much better range on the same index This fix changed some 'index' queries to 'range' queries in the test suite Don't create 'dummy' WHERE clause for trivial WHERE clauses where we can remove the WHERE clause. This fix removed of a lot of 'Using where' notes in the test suite. Give NOTE instead of WARNING if table/function doesn't exists when using DROP IF EXISTS Give NOTE instead of WARNING for safe field-type conversions
-
- 07 Sep, 2004 1 commit
-
-
guilhem@mysql.com authored
This does not fix any known bug, but is still a good idea.
-
- 29 Aug, 2004 1 commit
-
-
guilhem@mysql.com authored
We must not reset the charset in slave after each statement, otherwise the SET CHARACTER SET is cancelled immediately. Instead, we write a SET CHARACTER SET DEFAULT to the master's binlog when needed (like we already do for SET FOREIGN_KEY_CHECKS); such writing is not necessary in 4.1 (in 4.1 the bug does not exist, as the SET ONE_SHOT syntax is used). I have written a test and it works, but I'm not pushing the test as it requires building with all charsets. I have noticed differences between what is inserted in the master's table in 4.0 and 4.1, and alerted Bar.
-
- 26 Jul, 2004 1 commit
-
-
guilhem@mysql.com authored
(including one which may explain autobuild's failure of yesterday)
-
- 21 Jul, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 20 Jul, 2004 1 commit
-
-
guilhem@mysql.com authored
client code and replication slave code, as far as LOAD DATA INFILE and other queries' execution is concerned. Duplication of code leads to replication bugs, because the replication duplicate lags much behind. Fix for 2 Valgrind errors on slave replicating LOAD DATA INFILE - one serious (causing a random test failure in rpl_loaddata in 5.0) - one not serious (theoretically a bug but not dangerous): uninited thd->row_count
-
- 08 Jul, 2004 1 commit
-
-
monty@mysql.com authored
New handler::index_flags() definition to make it easy to check the full used key and a specific key part. Added key part to optimize_range() to fix problems when using fields in key parts.
-
- 30 Jun, 2004 1 commit
-
-
guilhem@mysql.com authored
processlist on slave": we now report in SHOW PROCESSLIST that we are writing to the temp files or loading the table. When we are writing to the tmp file: | 3 | system user | | | Connect | 6 | Making temp file /tmp/SQL_LOAD-2-1-2.data | and when we are actually loading the .data temp file into the table: | 3 | system user | | test | Connect | 2 | | LOAD DATA INFILE '/tmp/SQL_LOAD-2-1-2.data' INTO TABLE `t` <...> |
-
- 08 Jun, 2004 1 commit
-
-
guilhem@mysql.com authored
In mysqlbinlog, there was a problem with how we escaped the content of a string user variable. To be perfect, we should have escaped with character_set_client. But this charset is unknown to mysqlbinlog. So the simplest is to print the string in hex. This is unreadable but 100% safe with any charset (checked with Bar), no more need to bother with character_set_client.
-
- 03 Jun, 2004 1 commit
-
-
guilhem@mysql.com authored
by binlogging some SET ONE_SHOT CHARACTER_SETetc, which will be enough until we have it more compact and more complete in 5.0. With the present patch, replication will work ok between 4.1.3 master and slaves, as long as: - master and slave have the same GLOBAL.COLLATION_SERVER - COLLATION_DATABASE and CHARACTER_SET_DATABASE are not used - application does not use the fact that table is created with charset of the USEd db (BUG#2326). all of which are not too hard to fulfill. ONE_SHOT is reserved for internal use of mysqlbinlog|mysql and works only for charsets, so we give error if used for non-charset vars. Fix for BUG#3875 "mysqlbinlog produces wrong ouput if query uses variables containing quotes" and BUG#3943 "Queries with non-ASCII literals are not replicated properly after SET NAMES". Detecting that master and slave have different global charsets or server ids.
-
- 26 May, 2004 1 commit
-
-
hf@deer.(none) authored
-
- 17 May, 2004 1 commit
-
-
monty@mysql.com authored
-
- 14 May, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Fix remaining cases of Bug #3596: fix possible races caused by an obsolete value of thd->query_length in SHOW PROCESSLIST and SHOW INNODB STATUS; this fix depends on the fact that thd->query is always set to NULL before setting it to point to a new query
-
- 04 May, 2004 1 commit
-
-
guilhem@mysql.com authored
in hard-coded replication messages, always put small-length info (error codes, explanation of the error) at the beginning, so that it is not cut by truncation if the query is very long (which happens if the query goes first).
-
- 28 Apr, 2004 1 commit
-
-
pem@mysql.comhem.se authored
merged manually by guilhem.
-
- 07 Apr, 2004 2 commits
-
-
guilhem@mysql.com authored
if you are printing LOAD DATA INFILE and its USE as comments, don't update 'last_db' (because you have not actually changed the db in the server).
-
bell@sanja.is.com.ua authored
-
- 06 Apr, 2004 1 commit
-
-
guilhem@mysql.com authored
too big by 6 bytes. So I add code to substract 6 bytes if the master is 3.23. This is not perfect (because it won't work if the slave I/O thread has not noticed yet that the master is 3.23), but as long as the slave I/O thread starts Exec_master_log_pos will be ok. It must be merged to 4.1 but not to 5.0 (or it can be, because of #if MYSQL_VERSION_ID), because 5.0 already works if the master is 3.23 (and in a more natural way: in 5.0 we store the end_log_pos in the binlog and relay log). I had to move functions from slave.h to slave.cc to satisfy gcc.
-
- 05 Apr, 2004 1 commit
-
-
monty@mysql.com authored
Fixed bugs in group_concat with ORDER BY and DISTINCT (Bugs #2695, #3381 and #3319) Fixed crash when doing rollback in slave and the io thread catched up with the sql thread Set locked_in_memory properly
-
- 04 Apr, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
fixed error code in union test
-