monty@narttu.mysql.fi
77a70a0a24
merge with 4.0.15
2003-08-29 13:44:35 +03:00
monty@narttu.mysql.fi
27e331c30a
Revert change of lower-case-table handling as this breaks how alias works.
...
Changes like this should be done to 4.1, not to a stable release
2003-08-29 04:17:30 +03:00
monty@narttu.mysql.fi
a2a1e97226
Portability fixes
2003-08-28 22:18:02 +03:00
guilhem@mysql.com
6c9cff9534
Clearer states in SHOW PROCESSLIST for replication threads.
...
For example the Binlog_dump thread (on the master) sometimes showed "Slave:".
And there were confusing messages where "binlog" was employed instead
of "relay log".
2003-08-25 14:13:58 +02:00
Sinisa@sinisa.nasamreza.org
ced195f8a9
After merge fixes
2003-08-22 18:43:46 +03:00
guilhem@mysql.com
759a3c1e3c
2 minor edits, plus
...
fix for BUG#1113 "INSERT into non-trans table SELECT ; ROLLBACK" does not send warning"
and
fix for BUG#873 "In transaction, INSERT to non-trans table is written too early to binlog".
Now we don't always write the non-trans update immediately to the binlog;
if there is something in the binlog cache we write it to the binlog cache
(because the non-trans update could depend on a trans table which was modified
earlier in the transaction); then in case of ROLLBACK, we write the binlog
cache to the binlog, wrapped with BEGIN/ROLLBACK.
This guarantees that the slave does the same updates.
For ROLLBACK TO SAVEPOINT: when we execute a SAVEPOINT command we write it
to the binlog cache. At ROLLBACK TO SAVEPOINT, if some non-trans table was updated,
we write ROLLBACK TO SAVEPOINT to the binlog cache; when the transaction
terminates (COMMIT/ROLLBACK), the binlog cache will be flushed to the binlog
(because of the non-trans update) so we'll have SAVEPOINT and ROLLBACK TO
SAVEPOINT in the binlog.
Apart from this rare case of updates of mixed table types in transaction, the
usual way is still clear the binlog cache at ROLLBACK, or chop it at
ROLLBACK TO SAVEPOINT (meaning the SAVEPOINT command is also chopped, which
is fine).
Note that BUG#873 encompasses subbugs 1) and 2) of BUG#333 "3 binlogging bugs when doing INSERT with mixed InnoDB/MyISAM".
2003-08-22 15:39:24 +02:00
bell@laptop.sanja.is.com.ua
811ed77e5f
quick fix for found row counter
...
code cleunup
2003-08-20 21:57:37 +03:00
dlenev@mysql.com
bb96092202
Fix for BUG#1086. Now we don't preserve event's log_pos through
...
log-slave-updates since this causes unexpected values in
Exec_master_log_pos in A->B->C replication setup, synchronization
problems in master_pos_wait()...
Still this brokes some functionality in sql/repl_failsafe.cc
(but this file is not used now)
2003-08-20 03:38:31 +04:00
monty@mashka.mysql.fi
4f7512160b
After merge fixes
...
Use server character set if --default-character-set is not used
Added convert_string() for more efficient alloc+character-set convert of strings
2003-08-19 00:08:08 +03:00
monty@mashka.mysql.fi
2263e3e51f
Merge with 4.0.14
2003-08-11 22:44:43 +03:00
bell@sanja.is.com.ua
ddd3ee8b27
rewritten test using loop (BUG#930)
...
removed unused field (now it is in variables)
2003-08-08 23:27:22 +03:00
Sinisa@sinisa.nasamreza.org
e08a00bd02
Fuller implementation of lower case table names.
...
Bug record #828
2003-07-23 17:36:56 +03:00
monty@narttu.mysql.fi
df7c1e8165
Better fix for bug #791 : At binlog rotation, INSERTs may not find their way into the binlog
2003-07-14 14:59:26 +03:00
monty@mashka.mysql.fi
e1aa90a9bf
Safety and speedup fixes:
...
Changed is_open() to work as before.
Added back inited argument to LOG
2003-07-14 10:12:05 +03:00
guilhem@mysql.com
b7e1fe5ad1
Member no_rotate in MYSQL_LOG was always 0, I delete it.
2003-07-12 15:48:26 +02:00
guilhem@mysql.com
34c8918915
removed 2 small useless if().
2003-07-12 15:06:40 +02:00
guilhem@mysql.com
fbebac9a48
Fix for BUG#791:
...
a safer way of initing the mutexes in MYSQL_LOG.
is_open() is now always thread-safe.
See each file for details.
2003-07-11 14:26:44 +02:00
guilhem@mysql.com
9c73d91d54
WL#912 (more user control on relay logs):
...
FLUSH LOGS now rotates relay logs,
and a new variable max_relay_log_size.
Plus a very small bit of code cleaning.
2003-07-06 17:59:54 +02:00
monty@mashka.mysql.fi
baf9baba2a
merge
2003-07-01 15:57:45 +03:00
monty@mashka.mysql.fi
6bc7b3a6be
LAST_INSERT_ID() should not be set if we couldn't generate an auto_increment id.
2003-06-30 13:28:36 +03:00
monty@mashka.mysql.fi
34919a03c4
Added thread variable max_seeks_for_key
...
Change optimizer to prefer key lookups before table scan
Change table scans to be done after tables with constrains on scanned table
2003-06-27 03:04:54 +03:00
bell@sanja.is.com.ua
2d120d32fa
cond_count moved to SELECT_LEX_NODE
...
fixed BUG #726
2003-06-26 11:09:11 +03:00
monty@mashka.mysql.fi
5f556f11e0
Fixed memory allocation in Unique to not allocate too much memory
2003-06-26 07:56:55 +03:00
bar@bar.mysql.r18.ru
7371150f2d
New class DTCollation (SQL:2003 calls it "declared type collation")
...
It's a combination of collation and its derivation (precedence order)
2003-06-24 15:11:07 +05:00
gluh@gluh.mysql.r18.ru
289d375f50
SCRUM
...
Task ID 894:
Backport default_week_format variable to 4.0
2003-06-19 14:02:19 +05:00
igor@rurik.mysql.com
a0f3dcc3c8
Merge rurik.mysql.com:/home/igor/mysql-4.1
...
into rurik.mysql.com:/home/igor/dev/mysql-4.1-0
2003-06-12 06:22:35 -07:00
igor@rurik.mysql.com
f547f2769f
Many files:
...
New feature: preload indexes into key cache.
mi_preload.c:
new file
Many files:
Added preload statement.
2003-06-12 04:29:02 -07:00
bar@bar.mysql.r18.ru
81f0fb6e18
character_set_server is now updatable
...
character_set_database was added
Code optimization: reuse more code for all character sets variables
2003-05-30 13:03:56 +05:00
monty@mashka.mysql.fi
cb7061ebe4
merge
2003-05-22 02:57:27 +03:00
bar@bar.mysql.r18.ru
8d52377a5c
Some SHOW VARIABLES have been renamed:
...
collation_client -> character_set_client
collation_results -> character_set_results
character_set -> character_set_server
SET NAMES now doesn't start client->server conversion
SET CHARACTER SET now starts both client->server and server->client conversion
2003-05-21 17:44:12 +05:00
monty@narttu.mysql.fi
dd2b7918cd
Merge with 4.0.13
2003-05-19 16:35:49 +03:00
serg@serg.mylan
12e53eb9e1
parallel-repair available in mysqld
2003-05-04 18:43:37 +02:00
monty@narttu.mysql.fi
9e4f394e59
Fix reference to not initialized memory
...
Changed handing of priv_host to fix bug in FLUSH PRIVILEGES
2003-04-30 10:15:09 +03:00
venu@myvenu.com
eb137c063c
Support of warnings for all DML statements (Insert, Update and Alter)
...
Fix LOAD DATA INFILE warnings to have a better meanigful messages
Fix to make the mysql command line to automatically show the warnings count for all basic commands
2003-04-30 00:02:28 -07:00
serg@serg.mylan
d13e4fc532
CURRENT_USER() and "access denied" error messages now report hostname exactly as it was specified in the GRANT command (with wildcards, that is)
2003-04-29 00:15:18 +02:00
Sinisa@sinisa.nasamreza.org
5dc8dbea5f
merge fix
2003-04-26 15:26:28 +03:00
Sinisa@sinisa.nasamreza.org
3ca1a152eb
Making a better fix for double released pointers and safe
...
TMP_TABLE_PARAM.
This involved moving things around in include files.
All tests, including the ones with Valgrind passed.
2003-04-26 15:12:14 +03:00
guilhem@mysql.com
66e97ba570
Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.1
...
into mysql.com:/home/mysql_src/mysql-4.1
2003-04-24 17:42:07 +02:00
igor@hundin.mysql.fi
517a287ec9
Merge ibabaev@bk-internal.mysql.com:/home/bk/mysql-4.1
...
into hundin.mysql.fi:/home/igor/dev/mysql-4.1
2003-04-24 18:42:06 +03:00
guilhem@mysql.com
b03ec0d7db
Replication: new code to not modify in-memory log positions until the COMMIT
...
is executed, even if the transaction spans on >=2 relay logs (bug #53 ).
New variable relay_log_purge =0|1
New test to verify bug #53
2003-04-24 15:29:25 +02:00
igor@hundin.mysql.fi
80615fade2
Many files:
...
Added the MAX_LENGTH_FOR_SORT_DATA option
filesort.cc:
Added the MAX_LENGTH_FOR_SORT_DATA option
2003-04-24 14:33:33 +03:00
bar@bar.mysql.r18.ru
6d5f527afd
Variable names have been renamed:
...
client_collation -> collation_client
result_collation -> collation_results
connection_collation -> collation_connection
2003-04-23 18:19:22 +05:00
bar@bar.mysql.r18.ru
a3d08eaaf9
I renamed system variable literal_collation into connection_collation
2003-04-22 12:27:35 +05:00
venu@myvenu.com
24d5cd37d2
Merge bk-internal.mysql.com:/home/bk/mysql-4.1
...
into myvenu.com:/home/venu/work/sql/dev-4.1
2003-04-12 20:07:52 -07:00
bar@bar.mysql.r18.ru
8cf9ada977
Use of CHARSWT_INFO *result_collation
...
instead of bool convert_result_charset
SET CHARACTER SET inststead of SET NAMES in tests
2003-04-08 14:38:17 +05:00
bar@bar.mysql.r18.ru
e165845d39
sys_var_collation is now abstract class
...
Two separate classes sys_var_client_collation and sys_var_literal_collation have been added
for "literal_collation" and "client_collation" variables.
2003-04-07 16:10:27 +05:00
bar@bar.mysql.r18.ru
e0caf3f225
New methods to store strings with "convert to" argimument
2003-04-07 13:52:48 +05:00
venu@myvenu.com
06f075888e
Merge bk-internal.mysql.com:/home/bk/mysql-4.1
...
into myvenu.com:/home/venu/work/sql/dev-4.1
2003-04-04 13:25:53 -05:00
venu@myvenu.com
8eeecd9c86
Fix to support update + bianry logs with prepared statements (Dynamic query)
2003-04-04 12:33:17 -05:00
monty@narttu.mysql.fi
4a4838059f
Fixed bug in warning handling (Memory was allocated from wrong MEM_ROOT)
2003-04-03 21:19:14 +03:00