- 11 Nov, 2004 1 commit
-
-
paul@ice.snake.net authored
Handle some additional Texinfo tags that were being missed.
-
- 10 Nov, 2004 22 commits
-
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.1-clean
-
guilhem@mysql.com authored
no new message in 4.1 (causes merge issues with 5.0). Using ER_UNKNOW_ERROR and hardcoded message string instead.
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
monty@mysql.com authored
(Needed to check if memory allocated with mysql_once_init() has been freed)
-
kent@mysql.com authored
into mysql.com:/users/kboortz/daily/work/mysql-4.1-wax
-
guilhem@mysql.com authored
-
guilhem@mysql.com authored
WL#1596 "make mysqldump --master-data --single-transaction able to do online dump of InnoDB AND report reliable binlog coordinates corresponding to the dump". The good news is that now mysqldump can be used to get an online backup of InnoDB *which works for point-in-time recovery and replication slave creation*. Formerly, mysqldump --master-data --single-transaction used to call in fact mysqldump --master-data, so the dump was not an online dump (took big lock all time of dump). The only lock which is now taken in this patch is at the beginning of the dump: mysqldump does: FLUSH TABLES WITH READ LOCK; START TRANSACTION WITH CONSISTENT SNAPSHOT; SHOW MASTER STATUS; UNLOCK TABLES; so the lock time is in fact the time FLUSH TABLES WITH READ LOCK takes to return (can be 0 or very long, if a table is undergoing a huge update). I have done some more minor changes listed in the paragraph of mysqldump.c. WL#2237 "WITH CONSISTENT SNAPSHOT clause for START TRANSACTION": it's a START TRANSACTION which additionally starts a consistent read on all capable storage engine (i.e. InnoDB). So, can serve as a replacement for BEGIN; SELECT * FROM some_innodb_table LIMIT 1; which starts a consistent read too.
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
monty@mysql.com authored
Print position in normal log for Binlog dump
-
acurtis@pcgem.rdg.cyberkinetica.com authored
into pcgem.rdg.cyberkinetica.com:/usr/home/acurtis/work/bug6031
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
added new variable for ndb port 1186 changed meaning of ndb_port_base to be default tcp port setting changed to use split between port and port_base for ndbcluster so that ndb_port and ndb_port_base are propagated to startscript for ndbcluster added larger space to pid print moved readAndExecute out of CommandInterpreter to avoid linking lib with readline added c-api to Ndb_mgmclient pass also ndb_port to make
-
acurtis@pcgem.rdg.cyberkinetica.com authored
DROP DATABASE failed because of file ext not in TYPELIB of known extensions. General solution - construct a TYPELIB at runtime instead of a static list.
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
bar@mysql.com authored
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-4.1
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-4.1
-
wax@mysql.com authored
into mysql.com:/home/wax/mysql/mysql-4.1mysqltest
-
bar@mysql.com authored
the result takes its charset/collation attributes from the character string, e.g. SELECT func(NULL, _latin2'string') now returns a latin2 result. This is done by introducing a new derivation (aka coercibility) level DERIVATION_IGNORABLE, which is used with Item_null. 2. 'Pure' NULL is now BINARY(0), not CHAR(0). I.e. NULL is now more typeless.
-
wax@kishkin.ru authored
-
joreland@mysql.com authored
ndb: Fix return value in index_last wo/ rows
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1
-
- 09 Nov, 2004 13 commits
-
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-4.1
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
-
kent@mysql.com authored
into mysql.com:/users/kboortz/daily/work/mysql-4.1-wax
-
kent@mysql.com authored
Added Solaris compatibility
-
lars@mysql.com authored
into mysql.com:/home/bkroot/mysql-4.1
-
heikki@hundin.mysql.fi authored
Fix a bug in InnoDB code that fortunately was never used: row id is stored in a record always as a 6-byte unsigned integer, in a 'non-compressed' form
-
monty@mysql.com authored
Fix for valgrind/purify for variables that the compiler touches but that doesn't affect the outcome of the tests
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-4.1
-
joreland@mysql.com authored
-
lars@mysql.com authored
into mysql.com:/home/bkroot/mysql-4.1
-
monty@mysql.com authored
-
- 08 Nov, 2004 4 commits
-
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
guilhem@mysql.com authored
not know there's rollback (if it's because of a dupl row), better warn that it's happening. It can also be of use for a DBA killing a connection and wondering what this connection is still doing now. Example: | 5 | root | localhost | test | Killed | 10 | Rolling back | insert into i select * from j |
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
-