- 13 Jan, 2005 1 commit
-
-
unknown authored
into hundin.mysql.fi:/home/marko/k/mysql-4.0
-
- 12 Jan, 2005 6 commits
-
-
unknown authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
unknown authored
reported by Javier Fernandez-Sanguino Pena and Debian Security Audit Team (http://www.debian.org/security/audit)
-
unknown authored
case will be added to client_test in 4.1 sql/sql_parse.cc: A fix for bug #6761: "mysql_list_fields() does not work": init thd->query_length, which is used next line. Remove a stale comment.
-
unknown authored
open interface for setting the "delete-on-close" flag. innobase/os/os0file.c: Use system-supplied tmpfile() on Netware sql/ha_innodb.cc: Remove innobase_mysql_tmpfile() on Netware.
-
unknown authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0 sql/mysqld.cc: Auto merged
-
unknown authored
-
- 10 Jan, 2005 1 commit
-
-
unknown authored
mysql_admin_table() attempted to write to a vio which was 0. I could have fixed mysql_admin_table() but fixing my_net_write() looked more future-proof. sql/net_serv.cc: If no VIO, no write.
-
- 07 Jan, 2005 1 commit
-
-
unknown authored
Made the default --mail address to be <build@mysql.com>. Build-tools/Bootstrap: Made the default --mail address to be <build@mysql.com>.
-
- 06 Jan, 2005 2 commits
-
-
unknown authored
This happened only if my_write() couldn't write even one byte. I cannot easily add a .test for this, but I tested by hand before and after the change. mysys/my_write.c: Monty and I could not find a reason why a write should not wait for free disk space (if disk is full) because it could not write at least one byte; doing so certainly corrupts tables. my_pwrite() and my_fwrite() don't test for -1, so no problem.
-
unknown authored
build (to make the test suite pass) BUILD/compile-dist: - enable "with-extra-charsets=complex" for the distribution build (to make the test suite pass)
-
- 05 Jan, 2005 1 commit
-
-
unknown authored
official binary builds for Linux that are built against a static glibc with a 128k thread stack size limit can be compiled with a default that doesn't result in a harmless (but oft-misunderstood) warning message. (Bug #6226) include/my_pthread.h: Allow DEFAULT_THREAD_STACK to be set via -DDEFAULT_THREAD_STACK=...
-
- 04 Jan, 2005 1 commit
-
-
unknown authored
sql/set_var.cc: Make query_cache_wlock_invalidate visible in SHOW VARIABLES
-
- 03 Jan, 2005 1 commit
-
-
unknown authored
ChangeLog, too (to be more exact when tagging a release that's based on a merge ChangeSet) Build-tools/Bootstrap: - include merge ChangeSets into the ChangeLog, too (to be more exact when tagging a release that's based on a merge ChangeSet)
-
- 31 Dec, 2004 2 commits
- 30 Dec, 2004 3 commits
-
-
unknown authored
-
unknown authored
into mysql.com:/home/dlenev/src/mysql-4.0-bg7297
-
unknown authored
the Epoch". (With after review fixes). mysql-test/r/func_time.result: Added test for bug #7515 "from_unixtime(0) now returns NULL instead of the Epoch". mysql-test/t/func_time.test: Added test for bug #7515 "from_unixtime(0) now returns NULL instead of the Epoch". sql/item_timefunc.cc: Item_func_from_unixtime: from_unixtime(0) should return Epoch instead of NULL. sql/item_timefunc.h: Item_func_from_unixtime: - Removed unused method definition. - fix_length_and_dec() should set maybe_null to true since now from_unixtime() can return NULL even in case when none of its arguments is NULL.
-
- 27 Dec, 2004 2 commits
-
-
unknown authored
Fix the previous bug fix: dropping a table with FOREIGN KEY checks running on it caused a cascade of failed drops while the foreign key check was waiting for a lock innobase/row/row0mysql.c: Fix the previous bug fix: dropping a table with FOREIGN KEY checks running on it caused a cascade of failed drops while the foreign key check was waiting for a lock
-
unknown authored
Fix bug: if we dropped a table where an INSERT was waiting for a lock to check a FOREIGN KEY constraint, then an assertion would fail in lock_reset_all_on_table(), since that operation assumes no waiting locks on the table or its records row0mysql.c: Fix bug: InnoDB failed to drop a table in the background drop queue if the table was referenced by a foreign key constraint innobase/row/row0mysql.c: Fix bug: InnoDB failed to drop a table in the background drop queue if the table was referenced by a foreign key constraint innobase/row/row0ins.c: Fix bug: if we dropped a table where an INSERT was waiting for a lock to check a FOREIGN KEY constraint, then an assertion would fail in lock_reset_all_on_table(), since that operation assumes no waiting locks on the table or its records
-
- 24 Dec, 2004 1 commit
-
-
unknown authored
sql/mysqld.cc: A fix (bug #5652: [patch] tcpwrapper support is broken on systems using an unmodified tcpwrapper). Wrapper for fromhost, hosts_access, eval_client has been removed.
-
- 23 Dec, 2004 3 commits
-
-
unknown authored
into sinisa.nasamreza.org:/mnt/work/mysql-4.0
-
unknown authored
mysql-test/r/func_str.result: result for test case for a bug in QUOTE() (Bug #7495) mysql-test/t/func_str.test: test case for a bug in QUOTE() (Bug #7495) sql/item_strfunc.cc: a better fix for a QUOTE() bug (Bug #7495)
-
unknown authored
to behave well on 5.0 tables (well now you can't use tables from 4.1 and 5.0 with 4.0 because former use utf8, but still it is nice to have similar code in acl_init() and replace_user_table()). This also will make such GRANTs working in 5.0 (they are broken now). mysql-test/r/grant.result: Added test for GRANT which manipulates user limits. mysql-test/t/grant.test: Added test for GRANT which manipulates user limits.
-
- 22 Dec, 2004 2 commits
-
-
unknown authored
mysql-test/r/func_str.result: A result for test case for the bug #7495 involving either LTRIM() or TRIM() within QUOTE() function. mysql-test/t/func_str.test: A test case for the bug #7495 involving either LTRIM() or TRIM() within QUOTE() function. sql/item_strfunc.cc: Changes for LTRIM() and TRIM() functions that aleviate the bug entirely.
-
unknown authored
If AUTOCOMMIT=1, do not acquire an InnoDB table lock in LOCK TABLES; this makes porting of old MyISAM applications to InnoDB easier, since in that mode InnoDB table locks caused deadlocks very easily sql/ha_innodb.cc: If AUTOCOMMIT=1, do not acquire an InnoDB table lock in LOCK TABLES; this makes porting of old MyISAM applications to InnoDB easier, since in that mode InnoDB table locks caused deadlocks very easily
-
- 21 Dec, 2004 2 commits
-
-
unknown authored
Put back accidentally removed undef and remove a debug def innobase/os/os0file.c: Put back accidentally removed undef and remove a debug def
-
unknown authored
Fix InnoDB bug: on HP-UX, with a 32-bit binary, InnoDB was only able to read or write <= 2 GB files; the reason was that InnoDB treated the return value of lseek() as a 32-bit integer; lseek was used on HP-UX-11 as a replacement for pread() and pwrite() because HAVE_BROKEN_PREAD was defined on that platform innobase/os/os0file.c: Fix InnoDB bug: on HP-UX, with a 32-bit binary, InnoDB was only able to read or write <= 2 GB files; the reason was that InnoDB treated the return value of lseek() as a 32-bit integer; lseek was used on HP-UX-11 as a replacement for pread() and pwrite() because HAVE_BROKEN_PREAD was defined on that platform
-
- 20 Dec, 2004 1 commit
-
-
unknown authored
Increment from 4.0.23 to 4.0.24 configure.in: Increment from 4.0.23 to 4.0.24
-
- 18 Dec, 2004 5 commits
-
-
unknown authored
into ltantony.rdg.cyberkinetica.homeunix.net:/usr/home/antony/work/bug7391.4
-
unknown authored
-
unknown authored
-
unknown authored
-
unknown authored
Add in missing privilege checks. Tests for the privileges. mysql-test/r/grant.result: Bug#7391 - Multi-table UPDATE security regression Tests column, table and db level access mysql-test/t/grant.test: Bug#7391 - Multi-table UPDATE security regression Tests column, table and db level access sql/sql_update.cc: Bug#7391 - Multi-table UPDATE security regression Add in missing privilege checks.
-
- 16 Dec, 2004 5 commits
-
-
unknown authored
into mysql.com:/M40/mysql-4.0
-
unknown authored
mysql-test/mysql-test-run.sh: Backport an improvement from 4.1: If the tool is run with '--force', give a list of all test cases that failed at the end. This is essential for automated analysis of the build logs file.
-
unknown authored
mysql-test/r/update.result: moved drop statement mysql-test/t/update.test: moved drop statement
-
unknown authored
mysql-test/r/update.result: test results mysql-test/t/update.test: bug test
-
unknown authored
even with zero month and day" aka "Date decoding trouble" Two digit year should be interpreted correctly as year in 20th or 21st century even with zero month and day. Only exception should be zero date '00-00-00' or '00-00-00 00:00:00'. mysql-test/r/type_datetime.result: Added test for bug #7297 "Two digit year should be interpreted correctly even with zero month and day" mysql-test/t/type_datetime.test: Added test for bug #7297 "Two digit year should be interpreted correctly even with zero month and day" sql/time.cc: str_to_TIME(): Two digit year should be interpreted correctly as year in 20th or 21st century even with zero month and day. Only exception should be zero date '00-00-00' or '00-00-00 00:00:00'.
-