4 Commits

Author	SHA1	Message	Date
guilhem@mysql.com	d89f148de6	The automatic DROP TEMPORARY TABLE is now DROP TEMPORARY TABLE IF EXISTS, ... this is better in this case: - imagine user1 has created a temp table - imagine user2 does FLUSH TABLES WITH READ LOCK, then takes a backup, then RESET MASTER then UNLOCK TABLES, like mysqldump --first-slave - then in the binlog you will finally have the DROP TEMPORARY TABLE, but not the CREATE TEMPORARY TABLE, so when you later restore with mysqlbinlog|mysql, mysql will complain that table does not exist. Replication was already protected of this (it processes DROP TEMPORARY TABLE as if there was a IF EXISTS), now I add it directly to the query for mysqlbinlog|mysql to work.	2004-03-20 15:49:17 +01:00
guilhem@mysql.com	7234ed2681	fix for a random test failure on hpux/ia64 ... (a missing synchronization in the test)	2003-09-29 22:56:31 +02:00
monty@narttu.mysql.fi	89f30200bc	Removed random chars after filename for LOAD DATA INFILE (in mysqlbinlog) ... Add quoting for use `database` for mysqlbinlog Removed test ins0000001 Add support for --replace for exec in mysqltest Don't refer to install dir in mysqlbinlog.result	2003-09-29 12:31:35 +03:00
guilhem@mysql.com	9d7014c07b	Fix for BUG#1345 "SQL Syntax Error in binarylog with DROP TABLES": ... it's just backquoting the db's and table's names when writing DROP TEMPORARY TABLE to the binlog when a connection ends. A testcase for this.	2003-09-28 18:31:49 +02:00