MySQL 4.0.18 has been released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, MySQL 4.0.18, a new version of the popular Open Source/Free Software Database Management System, has been released. It is now available in source and binary form for a number of platforms from our download pages at http://www.mysql.com/downloads/ and mirror sites. Note that not all mirror sites may be up to date at this point in time - if you can't find this version on some mirror, please try again later or choose another download site. This is a bugfix release for the current production version. Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version. News from the ChangeLog: Functionality added or changed: * Fixed processing of `LOAD DATA' by `mysqlbinlog' in remote mode. (Bug #1378) * New utility program `myisam_ftdump' was added to binary distributions. * `mysqlhotcopy' now works on NetWare. * `ENGINE' is now a synonym for the `TYPE' option for `CREATE TABLE' and `ALTER TABLE'. * `lower_case_table_names' system variable now can take a value of `2', to store table names in mixed case on case-insensitive filesystems. * For replication of `HEAP' tables: Made the master automatically write a `DELETE FROM' statement to its binary log when a `HEAP' table is opened for the first time since master's startup. This is for the case where the slave has replicated a non-empty `HEAP' table, then the master is shut down and restarted: the table is now empty on master; the `DELETE FROM' empties it on slave too. Note that even with this fix, between the master's restart and the first use of the table on master, the slave still has out-of-date data in the table. But if you use the `init-file' option to populate the `HEAP' table on the master at startup, it ensures that the failing time interval is zero. (Bug #2477) * Optimizer is now better tuned for the case where the first used key part (of many) is a constant. (Bug #1679) * Removed old non-working `--old-rpl-compat' server option, which was a holdover from the very first 4.0.x versions. (Bug #2428) Bugs fixed: * Fixed bug when -init-file crashes MySQL if contains large select (Bug #2526) * `SHOW KEYS' now shows `NULL' in `Sub_part' column for `FULLTEXT' indexes. * The size of the signal thread's stack was increased to enable `mysqld' to run on Debian/ia64 with a TLS-enabled glibc. (Bug #2599) * Now one need only `SELECT' privilege for tables that are only read in `UPDATE' statements with many tables. (Bug #2377). * Give proper error message if one uses `LOCK TABLES ... ; INSERT ... SELECT' and one used the same table in the `INSERT' and `SELECT' part. (Bug #2296) * `SELECT INTO ... DUMPFILE' now deletes the generated file on error. * Fixed foreign key reference handling to allow references to column names that contain spaces. (Bug #1725) * Fixed problem with index reads on character fields with `BDB' tables. The symptom was that data could be returned in wrong lettercase. (Bug #2509) * Fixed a spurious table corruption problem that could sometimes appear on tables with indexed `TEXT' columns if these columns happened to contain values having trailing spaces. This bug was introduced in 4.0.17. * Fixed a problem where some queries could hang if a condition like `indexed_TEXT_column = expr' was present and the column contained values having trailing spaces. This bug was introduced in 4.0.17. * Fixed a bug that could cause incorrect results from a query that involved range conditions on indexed `TEXT' columns that happened to contain values having trailing spaces. This bug was introduced in 4.0.17. (Bug #2295) * Fixed incorrect path names in some of the manual pages. (Bug #2270) * Fixed spurious table corrupted errors in parallel repair operations. *Note `myisam_repair_threads': SHOW VARIABLES. * Fixed a crashing bug in parallel repair operations. *Note `myisam_repair_threads': SHOW VARIABLES. * Fixed bug in updating `MyISAM' tables for `BLOB' values longer than 16M. (Bug #2159) * Fixed bug in `mysqld_safe' when running multiple instances of MySQL. (Bug #2114) * Fixed a bug in using `HANDLER' statement with tables not from a current database. (Bug #2304) * Fix for a crashing bug that occurred due to the fact that multiple-table `UPDATE' statements did not check that there was only one table to be updated. (Bug #2103) * Fix for a crashing bug that occurred due to `BLOB' column type index size being calculated incorrectly in `MIN()' and `MAX()' optimizations. (Bug #2189) * Fix for a bug with incorrect syntax for `LOCK TABLES' in `mysqldump'. (Bug #2242) * Fixed a bug in `mysqld_safe' that caused
RE: MySQL 4.0.18 has been released
Hi, Can anyone tell where to find documentation on myisam_ftdump? I would like to know what myisam_ftdump is and how it differs from mysqldump. John -Original Message- From: Lenz Grimmer [mailto:[EMAIL PROTECTED] Sent: Friday, February 13, 2004 4:42 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: MySQL 4.0.18 has been released -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, MySQL 4.0.18, a new version of the popular Open Source/Free Software Database Management System, has been released. It is now available in source and binary form for a number of platforms from our download pages at http://www.mysql.com/downloads/ and mirror sites. Note that not all mirror sites may be up to date at this point in time - if you can't find this version on some mirror, please try again later or choose another download site. This is a bugfix release for the current production version. Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version. News from the ChangeLog: Functionality added or changed: * Fixed processing of `LOAD DATA' by `mysqlbinlog' in remote mode. (Bug #1378) * New utility program `myisam_ftdump' was added to binary distributions. * `mysqlhotcopy' now works on NetWare. * `ENGINE' is now a synonym for the `TYPE' option for `CREATE TABLE' and `ALTER TABLE'. * `lower_case_table_names' system variable now can take a value of `2', to store table names in mixed case on case-insensitive filesystems. * For replication of `HEAP' tables: Made the master automatically write a `DELETE FROM' statement to its binary log when a `HEAP' table is opened for the first time since master's startup. This is for the case where the slave has replicated a non-empty `HEAP' table, then the master is shut down and restarted: the table is now empty on master; the `DELETE FROM' empties it on slave too. Note that even with this fix, between the master's restart and the first use of the table on master, the slave still has out-of-date data in the table. But if you use the `init-file' option to populate the `HEAP' table on the master at startup, it ensures that the failing time interval is zero. (Bug #2477) * Optimizer is now better tuned for the case where the first used key part (of many) is a constant. (Bug #1679) * Removed old non-working `--old-rpl-compat' server option, which was a holdover from the very first 4.0.x versions. (Bug #2428) Bugs fixed: * Fixed bug when -init-file crashes MySQL if contains large select (Bug #2526) * `SHOW KEYS' now shows `NULL' in `Sub_part' column for `FULLTEXT' indexes. * The size of the signal thread's stack was increased to enable `mysqld' to run on Debian/ia64 with a TLS-enabled glibc. (Bug #2599) * Now one need only `SELECT' privilege for tables that are only read in `UPDATE' statements with many tables. (Bug #2377). * Give proper error message if one uses `LOCK TABLES ... ; INSERT ... SELECT' and one used the same table in the `INSERT' and `SELECT' part. (Bug #2296) * `SELECT INTO ... DUMPFILE' now deletes the generated file on error. * Fixed foreign key reference handling to allow references to column names that contain spaces. (Bug #1725) * Fixed problem with index reads on character fields with `BDB' tables. The symptom was that data could be returned in wrong lettercase. (Bug #2509) * Fixed a spurious table corruption problem that could sometimes appear on tables with indexed `TEXT' columns if these columns happened to contain values having trailing spaces. This bug was introduced in 4.0.17. * Fixed a problem where some queries could hang if a condition like `indexed_TEXT_column = expr' was present and the column contained values having trailing spaces. This bug was introduced in 4.0.17. * Fixed a bug that could cause incorrect results from a query that involved range conditions on indexed `TEXT' columns that happened to contain values having trailing spaces. This bug was introduced in 4.0.17. (Bug #2295) * Fixed incorrect path names in some of the manual pages. (Bug #2270) * Fixed spurious table corrupted errors in parallel repair operations. *Note `myisam_repair_threads': SHOW VARIABLES. * Fixed a crashing bug in parallel repair operations. *Note `myisam_repair_threads': SHOW VARIABLES. * Fixed bug in updating `MyISAM' tables for `BLOB' values longer than 16M. (Bug #2159) * Fixed bug in `mysqld_safe' when running multiple instances of MySQL. (Bug #2114) * Fixed a bug in using `HANDLER' statement with tables not from a current database. (Bug #2304) * Fix for a crashing bug that occurred due to the fact that multiple-table `UPDATE' statements did not check
Re: MySQL 4.0.18 has been released
In the last episode (Feb 13), John Griffin said:
Can anyone tell where to find documentation on myisam_ftdump? I would
like to know what myisam_ftdump is and how it differs from mysqldump.
It is a tool to dump the contents of a fulltext index. Mainly useful
for debugging.
Use: ft_dump table_name index_no
-d, --dump Dump index (incl. data offsets and word weights)
-s, --stats Report global stats
-v, --verbose Be verbose
-c, --count Calculate per-word stats (counts and global weights)
-l, --lengthReport length distribution
-e, --execute=name Execute given query
-h, --help Display help and exit
-?, --help Synonym for -h
Variables (--variable-name=value)
and boolean options {FALSE|TRUE} Value (after reading options)
- -
verbose FALSE
execute (No default value)
--
Dan Nelson
[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
