pkgsrc/databases/mysql-server/distinfo

15 lines
763 B
Text
Raw Normal View History

$NetBSD: distinfo,v 1.16 2002/06/03 14:08:27 tron Exp $
1999-07-09 15:50:05 +02:00
Updated mysql-server to 3.23.49 * Don't give warning for statement that is only a comment; This is needed for mysqldump --disable-keys to work. * Fixed unlikely caching bug when doing a join without keys. In this case the last used field for a table always returned NULL. * Added options to make LOAD DATA LOCAL INFILE more secure. * Added --xml option to mysqldump for producing XML output. * Changed to use autoconf 2.52 (from autoconf 2.13) * Fixed bug in complicated join with const tables. * Added internal safety checks for InnoDB. * Some InnoDB variables was always shown in SHOW VARIABLES as OFF on high-byte-first systems (like sparc). * Fixed problem with one thread using an InnoDB table and another thread doing an ALTER TABLE on the same table. Before that, mysqld could crash with an assertion failure in row0row.c, line 474. * Tuned the InnoDB SQL optimizer to favor more often index searches over table scans. SELECT queries will now also generally run faster on all platforms. * If MySQL binlogging is used, InnoDB now prints after crash recovery the latest MySQL binlog name and the offset InnoDB was able to recover to. This is useful, for example, when resynchronizing a master and a slave database in replication. * Added better error messages to help in installation problems of InnoDB tables. * One can now recover also MySQL temporary tables which have become orphaned inside the InnoDB tablespace. * InnoDB now prevents a FOREIGN KEY declaration where the signedness is not the same in the referencing and referenced integer columns. * Calling SHOW CREATE TABLE or SHOW TABLE STATUS could cause memory corruption and make mysqld to crash. Especially at risk was mysqldump, because it calls frequently SHOW CREATE TABLE. * If inserts to several tables containing an auto-inc column were wrapped inside one LOCK TABLES, InnoDB asserted in lock0lock.c. * In 3.23.47 we allowed several NULLS in a UNIQUE secondary index for an InnoDB table. But CHECK TABLE was not relaxed: it reports the table as corrupt. CHECK TABLE no longer complains in this situation. * SHOW GRANTS now shows REFERENCES instead of REFERENCE.
2002-03-18 15:17:43 +01:00
SHA1 (mysql-3.23.49.tar.gz) = 0256331c7aa9388955148f80cdca382f467ad1be
Size (mysql-3.23.49.tar.gz) = 11844905 bytes
SHA1 (patch-aa) = d40a52dd115b3fd4236d66c2c5946fddc04f13cb
SHA1 (patch-ab) = 8e80dc2b0def56f3453395f8310e71f8113c7ccd
SHA1 (patch-ac) = 29fbb5bac3a81c3f9197c2d9ff84b795cdfbcaed
SHA1 (patch-ad) = 7127dd00a6067aa06a563c13dde1ea25e70fa7bf
Updated mysql-server to 3.23.49 * Don't give warning for statement that is only a comment; This is needed for mysqldump --disable-keys to work. * Fixed unlikely caching bug when doing a join without keys. In this case the last used field for a table always returned NULL. * Added options to make LOAD DATA LOCAL INFILE more secure. * Added --xml option to mysqldump for producing XML output. * Changed to use autoconf 2.52 (from autoconf 2.13) * Fixed bug in complicated join with const tables. * Added internal safety checks for InnoDB. * Some InnoDB variables was always shown in SHOW VARIABLES as OFF on high-byte-first systems (like sparc). * Fixed problem with one thread using an InnoDB table and another thread doing an ALTER TABLE on the same table. Before that, mysqld could crash with an assertion failure in row0row.c, line 474. * Tuned the InnoDB SQL optimizer to favor more often index searches over table scans. SELECT queries will now also generally run faster on all platforms. * If MySQL binlogging is used, InnoDB now prints after crash recovery the latest MySQL binlog name and the offset InnoDB was able to recover to. This is useful, for example, when resynchronizing a master and a slave database in replication. * Added better error messages to help in installation problems of InnoDB tables. * One can now recover also MySQL temporary tables which have become orphaned inside the InnoDB tablespace. * InnoDB now prevents a FOREIGN KEY declaration where the signedness is not the same in the referencing and referenced integer columns. * Calling SHOW CREATE TABLE or SHOW TABLE STATUS could cause memory corruption and make mysqld to crash. Especially at risk was mysqldump, because it calls frequently SHOW CREATE TABLE. * If inserts to several tables containing an auto-inc column were wrapped inside one LOCK TABLES, InnoDB asserted in lock0lock.c. * In 3.23.47 we allowed several NULLS in a UNIQUE secondary index for an InnoDB table. But CHECK TABLE was not relaxed: it reports the table as corrupt. CHECK TABLE no longer complains in this situation. * SHOW GRANTS now shows REFERENCES instead of REFERENCE.
2002-03-18 15:17:43 +01:00
SHA1 (patch-ae) = 81fa0273261ea44c599cf44f5a3a56935c3a62bd
SHA1 (patch-af) = 78acdcd5a0f65ecaf545561eb3d450fa43746d1a
SHA1 (patch-ag) = 75634ff5c9ee61ff3ef61b1d9a4be4afc65e8754
SHA1 (patch-ah) = 7cd4278c9bdc5220de04f7e6b62bb8d11c892ffb
SHA1 (patch-ai) = 071e34cc9236b08cdc438afbb46801e66efc7e92
SHA1 (patch-aj) = 2e619c6f16a1256174fd3e6e4bca3214679a9347