kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/mysql51-server/PLIST

5088 lines
259 KiB
Text
Raw Normal View History

Changes 5.1.72: * InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index. * InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record. * InnoDB: InnoDB would rename a user-defined foreign key constraint containing the string “_ibfk_” in its name, resulting in a duplicate constraint. * InnoDB: Rolling back an INSERT after a failed BLOB write would result in an assertion failure. The assertion has been modified to allow NULL BLOB pointers if an error occurs during a BLOB write. * InnoDB: The srv_master_thread background thread, which monitors server activity and performs activities such as page flushing when the server is inactive or in a shutdown state, runs on a one second delay loop. srv_master_thread would fail to check if the server is in a shutdown state before sleeping. * InnoDB: An infinite loop could occur in buf_page_get_gen when handling compressed-only pages. * Within a stored program, comparison of the value of a scalar subquery with an IN clause resulted in an error for the first execution and raised an assertion for the second execution. * The my_strtoll10() function could incorrectly convert some long string-format numbers to numeric values and fail to set the overflow flag. * For queries that accessed an INFORMATION_SCHEMA table in a subquery, and attempt to lock a mutex that had already been locked could cause a server crash. * For DIV expressions, assignment of the result to multiple variables could cause a server crash. * mysqldump wrote SET statements as SET OPTION, which failed when reloaded because the deprecated OPTION keyword has been removed from SET syntax. * If one connection changed its default database and simultaneously another connection executed SHOW PROCESSLIST, the second connection could access invalid memory when attempting to display the first connection's default database. memory.
2013-10-01 13:00:39 +02:00
@comment $NetBSD: PLIST,v 1.24 2013/10/01 11:00:39 adam Exp $
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
bin/innochecksum
bin/my_print_defaults
bin/myisam_ftdump
bin/myisamchk
bin/myisamlog
bin/myisampack
bin/mysql.server
bin/mysql_client_test
${PLIST.embedded}bin/mysql_client_test_embedded
bin/mysql_install_db
bin/mysql_secure_installation
bin/mysql_tzinfo_to_sql
bin/mysql_waitpid
bin/mysqld_multi
bin/mysqld_safe
${PLIST.embedded}bin/mysqltest_embedded
Add mysqlmanager, ndb-cluster and pstack PKG_OPTIONS. These are control some optional functions for mysql51-server (leaf package). Bump PKGREVISION.
2010-03-21 15:41:41 +01:00
${PLIST.ndb}bin/ndb_config
${PLIST.ndb}bin/ndb_delete_all
${PLIST.ndb}bin/ndb_desc
${PLIST.ndb}bin/ndb_drop_index
${PLIST.ndb}bin/ndb_drop_table
${PLIST.ndb}bin/ndb_error_reporter
${PLIST.ndb}bin/ndb_mgm
${PLIST.ndb}bin/ndb_print_backup_file
${PLIST.ndb}bin/ndb_print_schema_file
${PLIST.ndb}bin/ndb_print_sys_file
${PLIST.ndb}bin/ndb_restore
${PLIST.ndb}bin/ndb_select_all
${PLIST.ndb}bin/ndb_select_count
${PLIST.ndb}bin/ndb_show_tables
${PLIST.ndb}bin/ndb_size.pl
${PLIST.ndb}bin/ndb_test_platform
${PLIST.ndb}bin/ndb_waiter
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
bin/perror
bin/replace
bin/resolve_stack_dump
bin/resolveip
Add mysqlmanager, ndb-cluster and pstack PKG_OPTIONS. These are control some optional functions for mysql51-server (leaf package). Bump PKGREVISION.
2010-03-21 15:41:41 +01:00
${PLIST.ndb}include/mysql/storage/ndb/mgmapi/mgmapi.h
${PLIST.ndb}include/mysql/storage/ndb/mgmapi/mgmapi_config_parameters.h
${PLIST.ndb}include/mysql/storage/ndb/mgmapi/mgmapi_config_parameters_debug.h
${PLIST.ndb}include/mysql/storage/ndb/mgmapi/mgmapi_debug.h
${PLIST.ndb}include/mysql/storage/ndb/mgmapi/mgmapi_error.h
${PLIST.ndb}include/mysql/storage/ndb/mgmapi/ndb_logevent.h
${PLIST.ndb}include/mysql/storage/ndb/mgmapi/ndbd_exit_codes.h
${PLIST.ndb}include/mysql/storage/ndb/ndb_constants.h
${PLIST.ndb}include/mysql/storage/ndb/ndb_init.h
${PLIST.ndb}include/mysql/storage/ndb/ndb_types.h
${PLIST.ndb}include/mysql/storage/ndb/ndb_version.h
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/Ndb.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbApi.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbBlob.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbDictionary.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbError.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbEventOperation.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbIndexOperation.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbIndexScanOperation.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbIndexStat.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbOperation.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbPool.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbRecAttr.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbReceiver.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbScanFilter.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbScanOperation.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/NdbTransaction.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/ndb_cluster_connection.hpp
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/ndb_opt_defaults.h
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/ndbapi_limits.h
${PLIST.ndb}include/mysql/storage/ndb/ndbapi/ndberror.h
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
lib/mysql/libdbug.a
lib/mysql/libheap.a
lib/mysql/libmyisam.a
lib/mysql/libmyisammrg.a
${PLIST.embedded}lib/mysql/libmysqld.a
lib/mysql/libmystrings.a
lib/mysql/libmysys.a
Add mysqlmanager, ndb-cluster and pstack PKG_OPTIONS. These are control some optional functions for mysql51-server (leaf package). Bump PKGREVISION.
2010-03-21 15:41:41 +01:00
${PLIST.ndb}lib/mysql/libndbclient.la
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
lib/mysql/libvio.a
lib/mysql/plugin/ha_archive.la
lib/mysql/plugin/ha_blackhole.la
lib/mysql/plugin/ha_example.la
lib/mysql/plugin/ha_federated.la
lib/mysql/plugin/ha_innodb_plugin.la
libexec/mysqld
Add mysqlmanager, ndb-cluster and pstack PKG_OPTIONS. These are control some optional functions for mysql51-server (leaf package). Bump PKGREVISION.
2010-03-21 15:41:41 +01:00
${PLIST.manager}libexec/mysqlmanager
${PLIST.ndb}libexec/ndb_cpcd
${PLIST.ndb}libexec/ndb_mgmd
${PLIST.ndb}libexec/ndbd
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
man/man1/mysqld_multi.1
man/man8/mysqld.8
man/man8/mysqlmanager.8
Add mysqlmanager, ndb-cluster and pstack PKG_OPTIONS. These are control some optional functions for mysql51-server (leaf package). Bump PKGREVISION.
2010-03-21 15:41:41 +01:00
${PLIST.ndb}man/man8/ndb_mgmd.8
${PLIST.ndb}man/man8/ndbd.8
${PLIST.ndb}man/man8/ndbmtd.8
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
mysql-test/lib/My/SafeProcess/my_safe_process
share/aclocal/mysql.m4
share/examples/rc.d/mysqld
share/mysql-test/collections/README
share/mysql-test/collections/README.experimental
share/mysql-test/collections/default.daily
share/mysql-test/collections/default.experimental
share/mysql-test/collections/default.push
share/mysql-test/collections/default.weekly
share/mysql-test/extra/binlog_tests/binlog.test
share/mysql-test/extra/binlog_tests/binlog_failure_mixing_engines.test
share/mysql-test/extra/binlog_tests/binlog_insert_delayed.test
share/mysql-test/extra/binlog_tests/binlog_truncate.test
share/mysql-test/extra/binlog_tests/blackhole.test
share/mysql-test/extra/binlog_tests/ctype_cp932.test
share/mysql-test/extra/binlog_tests/ctype_cp932_binlog.test
share/mysql-test/extra/binlog_tests/ctype_ucs_binlog.test
share/mysql-test/extra/binlog_tests/database.test
share/mysql-test/extra/binlog_tests/drop_temp_table.test
share/mysql-test/extra/binlog_tests/innodb_stat.test
share/mysql-test/extra/binlog_tests/insert_select-binlog.test
share/mysql-test/extra/binlog_tests/mix_innodb_myisam_binlog.test
share/mysql-test/extra/binlog_tests/mix_innodb_myisam_side_effects.test
Changes 5.1.67: Bug fixes http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-67.html
2013-01-21 09:58:43 +01:00
share/mysql-test/extra/binlog_tests/mysqlbinlog_row_engine.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/extra/rpl_tests/rpl_EE_err.test
share/mysql-test/extra/rpl_tests/rpl_auto_increment.test
share/mysql-test/extra/rpl_tests/rpl_auto_increment_insert_view.test
share/mysql-test/extra/rpl_tests/rpl_auto_increment_invoke_trigger.test
share/mysql-test/extra/rpl_tests/rpl_autoinc_func_invokes_trigger.test
share/mysql-test/extra/rpl_tests/rpl_blackhole.test
share/mysql-test/extra/rpl_tests/rpl_charset.test
share/mysql-test/extra/rpl_tests/rpl_commit_after_flush.test
share/mysql-test/extra/rpl_tests/rpl_conflicts.test
share/mysql-test/extra/rpl_tests/rpl_ddl.test
share/mysql-test/extra/rpl_tests/rpl_deadlock.test
share/mysql-test/extra/rpl_tests/rpl_delete_no_where.test
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/extra/rpl_tests/rpl_extra_col_master.test
share/mysql-test/extra/rpl_tests/rpl_extra_col_slave.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/extra/rpl_tests/rpl_failed_optimize.test
share/mysql-test/extra/rpl_tests/rpl_flsh_tbls.test
share/mysql-test/extra/rpl_tests/rpl_foreign_key.test
share/mysql-test/extra/rpl_tests/rpl_get_master_version_and_clock.test
share/mysql-test/extra/rpl_tests/rpl_insert_delayed.test
Update MySQL package to 5.1.56. Functionality added or changed: * mysqldump --xml now displays comments from column definitions. (Bug #13618) Bugs fixed: * InnoDB Storage Engine: InnoDB returned values for ¡Èrows examined¡É in the query plan that were higher than expected. NULL values were treated in an inconsistent way. The inaccurate statistics could trigger ¡Èfalse positives¡É in combination with the MAX_JOIN_SIZE setting, because the queries did not really examine as many rows as reported. (Bug #30423) * Partitioning: Trying to use the same column more than once in the partitioning key when partitioning a table by KEY caused mysqld to crash. Such duplication of key columns is now expressly disallowed, and fails with an appropriate error. (Bug #53354, Bug #57924) * Replication: When using the statement-based logging format, INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements affecting transactional tables that did not fail were not written to the binary log if they did not insert any rows. (With statement-based logging, all successful statements should be logged, whether they do or do not cause any rows to be changed.) (Bug #59338) * Replication: Formerly, STOP SLAVE stopped the slave I/O thread first and then stopped the slave SQL thread; thus, it was possible for the I/O thread to stop after replicating only part of a transaction which the SQL thread was executing, in wich case¡½if the transaction could not be rolled back safely¡½the SQL thread could hang. Now, STOP SLAVE stops the slave SQL thread first and then stops the I/O thread; this guarantees that the I/O thread can fetch any remaining events in the transaction that the SQL thread is executing, so that the SQL thread can finish the transaction if it cannot be rolled back safely. (Bug #58546) * A query of the following form returned an incorrect result, where the values for col_name in the result set were entirely replaced with NULL values: SELECT DISTINCT col_name ... ORDER BY col_name DESC; (Bug #59308, Bug #11766241) * DELETE or UPDATE statements could fail if they used DATE or DATETIME values with a year, month, or day part of zero. (Bug #59173) * The ESCAPE clause for the LIKE operator allows only expressions that evaluate to a constant at execution time, but aggregrate functions were not being rejected. (Bug #59149) * Memory leaks detected by Valgrind, some of which could cause incorrect query results, were corrected. (Bug #59110, Bug #11766075) mysqlslap failed to check for a NULL return from mysql_store_result() and crashed trying to process the result set. (Bug #59109) * In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could cause a server crash. (Bug #58371) * When mysqldadmin was run with the --sleep and --count options, it went into an infinite loop executing the specified command. (Bug #58221) * Some string manipulating SQL functions use a shared string object intended to contain an immutable empty string. This object was used by the SQL function SUBSTRING_INDEX() to return an empty string when one argument was of the wrong datatype. If the string object was then modified by the SQL function INSERT(), undefined behavior ensued. (Bug #58165, Bug #11765225) * Parsing nested regular expressions could lead to recursion resulting in a stack overflow crash. (Bug #58026, Bug #11765099) * The mysql client went into an infinite loop if the standard input was a directory. (Bug #57450) * The expression const1 BETWEEN const2 AND field was optimized incorrectly and produced incorrect results. (Bug #57030, Bug #11764215) * Some RPM installation scripts used a hardcoded value for the data directory, which could result in a failed installation for users who have a nonstandard data directory location. The same was true for other configuration values such as the PID file name. (Bug #56581, Bug #11763817) * On FreeBSD and OpenBSD, the server incorrectly checked the range of the system date, causing legal values to be rejected. (Bug #55755, Bug #11763089) * When using ExtractValue() or UpdateXML(), if the XML to be read contained an incomplete XML comment, MySQL read beyond the end of the XML string when processing, leading to a crash of the server. (Bug #44332)
2011-03-08 15:06:43 +01:00
share/mysql-test/extra/rpl_tests/rpl_insert_duplicate.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/extra/rpl_tests/rpl_insert_id.test
share/mysql-test/extra/rpl_tests/rpl_insert_id_pk.test
share/mysql-test/extra/rpl_tests/rpl_insert_ignore.test
share/mysql-test/extra/rpl_tests/rpl_loaddata.test
share/mysql-test/extra/rpl_tests/rpl_loadfile.test
share/mysql-test/extra/rpl_tests/rpl_log.test
share/mysql-test/extra/rpl_tests/rpl_max_relay_size.test
share/mysql-test/extra/rpl_tests/rpl_mixing_engines.inc
share/mysql-test/extra/rpl_tests/rpl_mixing_engines.test
share/mysql-test/extra/rpl_tests/rpl_multi_query.test
share/mysql-test/extra/rpl_tests/rpl_multi_update.test
share/mysql-test/extra/rpl_tests/rpl_multi_update2.test
share/mysql-test/extra/rpl_tests/rpl_multi_update3.test
share/mysql-test/extra/rpl_tests/rpl_ndb_2multi_basic.test
share/mysql-test/extra/rpl_tests/rpl_ndb_2multi_eng.test
share/mysql-test/extra/rpl_tests/rpl_ndb_apply_status.test
share/mysql-test/extra/rpl_tests/rpl_not_null.test
share/mysql-test/extra/rpl_tests/rpl_partition.test
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/extra/rpl_tests/rpl_record_compare.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/extra/rpl_tests/rpl_relayrotate.test
share/mysql-test/extra/rpl_tests/rpl_reset_slave.test
share/mysql-test/extra/rpl_tests/rpl_row_001.test
share/mysql-test/extra/rpl_tests/rpl_row_UUID.test
share/mysql-test/extra/rpl_tests/rpl_row_basic.test
share/mysql-test/extra/rpl_tests/rpl_row_blob.test
share/mysql-test/extra/rpl_tests/rpl_row_delayed_ins.test
share/mysql-test/extra/rpl_tests/rpl_row_func003.test
share/mysql-test/extra/rpl_tests/rpl_row_sp002.test
share/mysql-test/extra/rpl_tests/rpl_row_sp003.test
share/mysql-test/extra/rpl_tests/rpl_row_sp006.test
share/mysql-test/extra/rpl_tests/rpl_row_sp007.test
share/mysql-test/extra/rpl_tests/rpl_row_tabledefs.test
share/mysql-test/extra/rpl_tests/rpl_set_null.test
share/mysql-test/extra/rpl_tests/rpl_stm_EE_err2.test
Update mysql51-{client,server} package to 5.1.51, MySQL 5.1.51. For full changes, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html Here is summary for security fixes: * Security Fix: During evaluation of arguments to extreme-value functions (such as LEAST() and GREATEST()), type errors did not propagate properly, causing the server to crash. (Bug#55826) * Security Fix: The server could crash after materializing a derived table that required a temporary table for grouping. (Bug#55568) * Security Fix: A user-variable assignment expression that is evaluated in a logical expression context can be precalculated in a temporary table for GROUP BY. However, when the expression value is used after creation of the temporary table, it was re-evaluated, not read from the table and a server crash resulted. (Bug#55564) * Security Fix: Pre-evaluation of LIKE predicates during view preparation could cause a server crash. (Bug#54568) * Security Fix: GROUP_CONCAT() and WITH ROLLUP together could cause a server crash. (Bug#54476) * Security Fix: Queries could cause a server crash if the GREATEST() or LEAST() function had a mixed list of numeric and LONGBLOB arguments, and the result of such a function was processed using an intermediate temporary table. (Bug#54461) * Security Fix: Queries with nested joins could cause an infinite loop in the server when used from stored procedures and prepared statements. (Bug#53544) * Security Fix: The PolyFromWKB() function could crash the server when improper WKB data was passed to the function. (Bug#51875)
2010-10-06 14:37:58 +02:00
share/mysql-test/extra/rpl_tests/rpl_stm_create_if_not_exists.test
Update mysql51-{client,server} to 5.1.53. Most changes are related to replication and seems to no security fix. For more detail, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html
2010-11-26 14:52:58 +01:00
share/mysql-test/extra/rpl_tests/rpl_stop_slave.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/extra/rpl_tests/rpl_sv_relay_space.test
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/extra/rpl_tests/rpl_test_framework.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/extra/rpl_tests/rpl_tmp_table_and_DDL.test
share/mysql-test/extra/rpl_tests/rpl_trig004.test
share/mysql-test/extra/rpl_tests/rpl_truncate.test
share/mysql-test/extra/rpl_tests/rpl_truncate_helper.test
share/mysql-test/include/add_anonymous_users.inc
share/mysql-test/include/analyze-sync_with_master.test
share/mysql-test/include/analyze-timeout.test
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/assert.inc
share/mysql-test/include/begin_include_file.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/big_test.inc
share/mysql-test/include/binlog_inject_error.inc
share/mysql-test/include/check-testcase.test
share/mysql-test/include/check-warnings.test
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/include/check_concurrent_insert.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/check_events_off.inc
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/include/check_no_concurrent_insert.inc
share/mysql-test/include/check_no_row_lock.inc
share/mysql-test/include/check_shared_row_lock.inc
share/mysql-test/include/check_slave_is_running.inc
share/mysql-test/include/check_slave_no_error.inc
share/mysql-test/include/check_slave_param.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/check_var_limit.inc
share/mysql-test/include/cleanup_fake_relay_log.inc
share/mysql-test/include/commit.inc
share/mysql-test/include/common-tests.inc
share/mysql-test/include/concurrent.inc
share/mysql-test/include/connect2.inc
share/mysql-test/include/count_sessions.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/ctype_8bit.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/ctype_common.inc
share/mysql-test/include/ctype_filesort.inc
share/mysql-test/include/ctype_german.inc
share/mysql-test/include/ctype_innodb_like.inc
share/mysql-test/include/ctype_like_escape.inc
share/mysql-test/include/ctype_like_range_f1f2.inc
share/mysql-test/include/ctype_regex.inc
share/mysql-test/include/ddl_i18n.check_events.inc
share/mysql-test/include/ddl_i18n.check_sp.inc
share/mysql-test/include/ddl_i18n.check_triggers.inc
share/mysql-test/include/ddl_i18n.check_views.inc
share/mysql-test/include/deadlock.inc
share/mysql-test/include/default_my.cnf
share/mysql-test/include/default_mysqld.cnf
share/mysql-test/include/default_ndbd.cnf
share/mysql-test/include/delete_anonymous_users.inc
share/mysql-test/include/diff_tables.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/end_include_file.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/endspace.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/file_does_not_exist.inc
share/mysql-test/include/force_restart.inc
share/mysql-test/include/force_restart_if_skipped.inc
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/include/get_relay_log_pos.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/gis_generic.inc
share/mysql-test/include/gis_keys.inc
share/mysql-test/include/grant_cache.inc
share/mysql-test/include/handler.inc
share/mysql-test/include/have_32bit.inc
share/mysql-test/include/have_64bit.inc
share/mysql-test/include/have_archive.inc
share/mysql-test/include/have_big5.inc
share/mysql-test/include/have_binlog_format_mixed.inc
share/mysql-test/include/have_binlog_format_mixed_or_row.inc
share/mysql-test/include/have_binlog_format_mixed_or_statement.inc
share/mysql-test/include/have_binlog_format_row.inc
share/mysql-test/include/have_binlog_format_row_or_statement.inc
share/mysql-test/include/have_binlog_format_statement.inc
share/mysql-test/include/have_blackhole.inc
share/mysql-test/include/have_case_insensitive_file_system.inc
share/mysql-test/include/have_case_insensitive_fs.inc
share/mysql-test/include/have_case_sensitive_file_system.inc
share/mysql-test/include/have_community_features.inc
share/mysql-test/include/have_compress.inc
share/mysql-test/include/have_cp1250_ch.inc
share/mysql-test/include/have_cp1251.inc
share/mysql-test/include/have_cp866.inc
share/mysql-test/include/have_cp932.inc
share/mysql-test/include/have_crypt.inc
share/mysql-test/include/have_csv.inc
Update MySQL package to 5.1.56. Functionality added or changed: * mysqldump --xml now displays comments from column definitions. (Bug #13618) Bugs fixed: * InnoDB Storage Engine: InnoDB returned values for ¡Èrows examined¡É in the query plan that were higher than expected. NULL values were treated in an inconsistent way. The inaccurate statistics could trigger ¡Èfalse positives¡É in combination with the MAX_JOIN_SIZE setting, because the queries did not really examine as many rows as reported. (Bug #30423) * Partitioning: Trying to use the same column more than once in the partitioning key when partitioning a table by KEY caused mysqld to crash. Such duplication of key columns is now expressly disallowed, and fails with an appropriate error. (Bug #53354, Bug #57924) * Replication: When using the statement-based logging format, INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements affecting transactional tables that did not fail were not written to the binary log if they did not insert any rows. (With statement-based logging, all successful statements should be logged, whether they do or do not cause any rows to be changed.) (Bug #59338) * Replication: Formerly, STOP SLAVE stopped the slave I/O thread first and then stopped the slave SQL thread; thus, it was possible for the I/O thread to stop after replicating only part of a transaction which the SQL thread was executing, in wich case¡½if the transaction could not be rolled back safely¡½the SQL thread could hang. Now, STOP SLAVE stops the slave SQL thread first and then stops the I/O thread; this guarantees that the I/O thread can fetch any remaining events in the transaction that the SQL thread is executing, so that the SQL thread can finish the transaction if it cannot be rolled back safely. (Bug #58546) * A query of the following form returned an incorrect result, where the values for col_name in the result set were entirely replaced with NULL values: SELECT DISTINCT col_name ... ORDER BY col_name DESC; (Bug #59308, Bug #11766241) * DELETE or UPDATE statements could fail if they used DATE or DATETIME values with a year, month, or day part of zero. (Bug #59173) * The ESCAPE clause for the LIKE operator allows only expressions that evaluate to a constant at execution time, but aggregrate functions were not being rejected. (Bug #59149) * Memory leaks detected by Valgrind, some of which could cause incorrect query results, were corrected. (Bug #59110, Bug #11766075) mysqlslap failed to check for a NULL return from mysql_store_result() and crashed trying to process the result set. (Bug #59109) * In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could cause a server crash. (Bug #58371) * When mysqldadmin was run with the --sleep and --count options, it went into an infinite loop executing the specified command. (Bug #58221) * Some string manipulating SQL functions use a shared string object intended to contain an immutable empty string. This object was used by the SQL function SUBSTRING_INDEX() to return an empty string when one argument was of the wrong datatype. If the string object was then modified by the SQL function INSERT(), undefined behavior ensued. (Bug #58165, Bug #11765225) * Parsing nested regular expressions could lead to recursion resulting in a stack overflow crash. (Bug #58026, Bug #11765099) * The mysql client went into an infinite loop if the standard input was a directory. (Bug #57450) * The expression const1 BETWEEN const2 AND field was optimized incorrectly and produced incorrect results. (Bug #57030, Bug #11764215) * Some RPM installation scripts used a hardcoded value for the data directory, which could result in a failed installation for users who have a nonstandard data directory location. The same was true for other configuration values such as the PID file name. (Bug #56581, Bug #11763817) * On FreeBSD and OpenBSD, the server incorrectly checked the range of the system date, causing legal values to be rejected. (Bug #55755, Bug #11763089) * When using ExtractValue() or UpdateXML(), if the XML to be read contained an incomplete XML comment, MySQL read beyond the end of the XML string when processing, leading to a crash of the server. (Bug #44332)
2011-03-08 15:06:43 +01:00
share/mysql-test/include/have_dbi_dbd-mysql.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/have_debug.inc
share/mysql-test/include/have_debug_sync.inc
share/mysql-test/include/have_dynamic_loading.inc
share/mysql-test/include/have_eucjpms.inc
share/mysql-test/include/have_euckr.inc
share/mysql-test/include/have_example_plugin.inc
share/mysql-test/include/have_exampledb.inc
Changes 5.1.60: * Upgrading from an Advanced GPL RPM package to an Advanced RPM package did not work. Now on Linux it is possible to use rpm -U to replace any installed MySQL product by any other of the same release family. It is not necessary to remove the old produce with rpm -e first. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. Bugs Fixed * Important Change: InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Replication: Issuing the following statements, in the order shown, could cause a deadlock between the user thread and I/O thread. * more...
2011-12-02 15:25:09 +01:00
share/mysql-test/include/have_federated_plugin.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/have_gb2312.inc
share/mysql-test/include/have_gbk.inc
share/mysql-test/include/have_geometry.inc
share/mysql-test/include/have_innodb.inc
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/include/have_innodb_plugin.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/have_koi8r.inc
share/mysql-test/include/have_latin2_ch.inc
share/mysql-test/include/have_local_infile.inc
share/mysql-test/include/have_log_bin.inc
share/mysql-test/include/have_lowercase0.inc
share/mysql-test/include/have_lowercase1.inc
share/mysql-test/include/have_lowercase2.inc
share/mysql-test/include/have_multi_ndb.inc
share/mysql-test/include/have_mysql_upgrade.inc
share/mysql-test/include/have_ndb.inc
share/mysql-test/include/have_ndb_extra.inc
share/mysql-test/include/have_ndbapi_examples.inc
share/mysql-test/include/have_not_innodb_plugin.inc
share/mysql-test/include/have_outfile.inc
share/mysql-test/include/have_partition.inc
share/mysql-test/include/have_query_cache.inc
share/mysql-test/include/have_simple_parser.inc
share/mysql-test/include/have_sjis.inc
share/mysql-test/include/have_ssl.inc
share/mysql-test/include/have_symlink.inc
share/mysql-test/include/have_tis620.inc
share/mysql-test/include/have_ucs2.inc
share/mysql-test/include/have_udf.inc
share/mysql-test/include/have_ujis.inc
share/mysql-test/include/have_utf8.inc
Changes 5.1.72: * InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index. * InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record. * InnoDB: InnoDB would rename a user-defined foreign key constraint containing the string “_ibfk_” in its name, resulting in a duplicate constraint. * InnoDB: Rolling back an INSERT after a failed BLOB write would result in an assertion failure. The assertion has been modified to allow NULL BLOB pointers if an error occurs during a BLOB write. * InnoDB: The srv_master_thread background thread, which monitors server activity and performs activities such as page flushing when the server is inactive or in a shutdown state, runs on a one second delay loop. srv_master_thread would fail to check if the server is in a shutdown state before sleeping. * InnoDB: An infinite loop could occur in buf_page_get_gen when handling compressed-only pages. * Within a stored program, comparison of the value of a scalar subquery with an IN clause resulted in an error for the first execution and raised an assertion for the second execution. * The my_strtoll10() function could incorrectly convert some long string-format numbers to numeric values and fail to set the overflow flag. * For queries that accessed an INFORMATION_SCHEMA table in a subquery, and attempt to lock a mutex that had already been locked could cause a server crash. * For DIV expressions, assignment of the result to multiple variables could cause a server crash. * mysqldump wrote SET statements as SET OPTION, which failed when reloaded because the deprecated OPTION keyword has been removed from SET syntax. * If one connection changed its default database and simultaneously another connection executed SHOW PROCESSLIST, the second connection could access invalid memory when attempting to display the first connection's default database. memory.
2013-10-01 13:00:39 +02:00
share/mysql-test/include/have_valgrind.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/index_merge1.inc
share/mysql-test/include/index_merge2.inc
share/mysql-test/include/index_merge_2sweeps.inc
share/mysql-test/include/index_merge_ror.inc
share/mysql-test/include/index_merge_ror_cpk.inc
share/mysql-test/include/innodb_rollback_on_timeout.inc
share/mysql-test/include/innodb_trx_weight.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/io_thd_fault_injection.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/is_embedded.inc
share/mysql-test/include/kill_query.inc
share/mysql-test/include/kill_query_and_diff_master_slave.inc
share/mysql-test/include/linux_sys_vars.inc
share/mysql-test/include/load_sysvars.inc
share/mysql-test/include/loaddata_autocom.inc
share/mysql-test/include/master-slave.inc
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/include/min_null_cond.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/mix1.inc
share/mysql-test/include/mix2.inc
share/mysql-test/include/mix2_ucs2.inc
share/mysql-test/include/mtr_check.sql
share/mysql-test/include/mtr_warnings.sql
Update mysql51 to 5.1.65. While here, let to use OpenSSL instead of internal yaSSL with ssl option, may related to PR 46912. Changes in MySQL 5.1.65 (2012-08-09) Functionality Added or Changed * Important Change: The YEAR(2) data type is now deprecated because it is problematic. Support for YEAR(2) will be removed in a future release of MySQL. For more information, see Section 11.3.4, "YEAR(2) Limitations and Migrating to YEAR(4)". Bugs Fixed * The server did not build with gcc 4.7. (Bug #14238406) Changes in MySQL 5.1.64 (Not released) Functionality Added or Changed * Important Change: Replication: The SHOW BINARY LOGS statement (and its equivalent SHOW MASTER LOGS) may now be executed by a user with the REPLICATION CLIENT privilege. (Formerly, the SUPER privilege was necessary to use either form of this statement.)
2012-09-15 16:48:57 +02:00
share/mysql-test/include/mysqlbinlog_have_debug.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/mysqldump.inc
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/include/mysqlhotcopy.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/mysqltest-x.inc
share/mysql-test/include/ndb_backup.inc
share/mysql-test/include/ndb_backup_print.inc
share/mysql-test/include/ndb_default_cluster.inc
share/mysql-test/include/ndb_master-slave.inc
share/mysql-test/include/ndb_master-slave_2ch.inc
share/mysql-test/include/ndb_not_readonly.inc
share/mysql-test/include/ndb_restore_master.inc
share/mysql-test/include/ndb_restore_slave_eoption.inc
share/mysql-test/include/ndb_setup_slave.inc
share/mysql-test/include/ndb_wait_connected.inc
share/mysql-test/include/no_running_event_scheduler.inc
share/mysql-test/include/no_running_events.inc
share/mysql-test/include/no_valgrind_without_big.inc
share/mysql-test/include/not_as_root.inc
Update mysql51-client/mysql51-server package to 5.1.45. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html Added a patch for recent security problem to mysql51-server, too. http://secunia.com/advisories/39454
2010-04-21 00:58:10 +02:00
share/mysql-test/include/not_binlog_format_row.inc
Update mysql51-{client,server} package to 5.1.51, MySQL 5.1.51. For full changes, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html Here is summary for security fixes: * Security Fix: During evaluation of arguments to extreme-value functions (such as LEAST() and GREATEST()), type errors did not propagate properly, causing the server to crash. (Bug#55826) * Security Fix: The server could crash after materializing a derived table that required a temporary table for grouping. (Bug#55568) * Security Fix: A user-variable assignment expression that is evaluated in a logical expression context can be precalculated in a temporary table for GROUP BY. However, when the expression value is used after creation of the temporary table, it was re-evaluated, not read from the table and a server crash resulted. (Bug#55564) * Security Fix: Pre-evaluation of LIKE predicates during view preparation could cause a server crash. (Bug#54568) * Security Fix: GROUP_CONCAT() and WITH ROLLUP together could cause a server crash. (Bug#54476) * Security Fix: Queries could cause a server crash if the GREATEST() or LEAST() function had a mixed list of numeric and LONGBLOB arguments, and the result of such a function was processed using an intermediate temporary table. (Bug#54461) * Security Fix: Queries with nested joins could cause an infinite loop in the server when used from stored procedures and prepared statements. (Bug#53544) * Security Fix: The PolyFromWKB() function could crash the server when improper WKB data was passed to the function. (Bug#51875)
2010-10-06 14:37:58 +02:00
share/mysql-test/include/not_blackhole.inc
Update mysql51-{client,server} package to 5.1.57. This is simply maintenance release, no security fix. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-57.html in detail.
2011-05-08 18:01:57 +02:00
share/mysql-test/include/not_crashrep.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/not_embedded.inc
share/mysql-test/include/not_ndb.inc
share/mysql-test/include/not_ndb_default.inc
share/mysql-test/include/not_openssl.inc
share/mysql-test/include/not_valgrind.inc
share/mysql-test/include/not_windows.inc
share/mysql-test/include/not_windows_embedded.inc
share/mysql-test/include/one_thread_per_connection.inc
share/mysql-test/include/parser_bug21114.inc
share/mysql-test/include/partition_date_range.inc
share/mysql-test/include/ps_conv.inc
share/mysql-test/include/ps_create.inc
share/mysql-test/include/ps_ddl_1.inc
share/mysql-test/include/ps_modify.inc
share/mysql-test/include/ps_modify1.inc
share/mysql-test/include/ps_query.inc
share/mysql-test/include/ps_renew.inc
share/mysql-test/include/query_cache.inc
share/mysql-test/include/query_cache_sql_prepare.inc
share/mysql-test/include/read_many_rows.inc
share/mysql-test/include/report-features.test
share/mysql-test/include/restart_mysqld.inc
Update MySQL package to 5.1.56. Functionality added or changed: * mysqldump --xml now displays comments from column definitions. (Bug #13618) Bugs fixed: * InnoDB Storage Engine: InnoDB returned values for ¡Èrows examined¡É in the query plan that were higher than expected. NULL values were treated in an inconsistent way. The inaccurate statistics could trigger ¡Èfalse positives¡É in combination with the MAX_JOIN_SIZE setting, because the queries did not really examine as many rows as reported. (Bug #30423) * Partitioning: Trying to use the same column more than once in the partitioning key when partitioning a table by KEY caused mysqld to crash. Such duplication of key columns is now expressly disallowed, and fails with an appropriate error. (Bug #53354, Bug #57924) * Replication: When using the statement-based logging format, INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements affecting transactional tables that did not fail were not written to the binary log if they did not insert any rows. (With statement-based logging, all successful statements should be logged, whether they do or do not cause any rows to be changed.) (Bug #59338) * Replication: Formerly, STOP SLAVE stopped the slave I/O thread first and then stopped the slave SQL thread; thus, it was possible for the I/O thread to stop after replicating only part of a transaction which the SQL thread was executing, in wich case¡½if the transaction could not be rolled back safely¡½the SQL thread could hang. Now, STOP SLAVE stops the slave SQL thread first and then stops the I/O thread; this guarantees that the I/O thread can fetch any remaining events in the transaction that the SQL thread is executing, so that the SQL thread can finish the transaction if it cannot be rolled back safely. (Bug #58546) * A query of the following form returned an incorrect result, where the values for col_name in the result set were entirely replaced with NULL values: SELECT DISTINCT col_name ... ORDER BY col_name DESC; (Bug #59308, Bug #11766241) * DELETE or UPDATE statements could fail if they used DATE or DATETIME values with a year, month, or day part of zero. (Bug #59173) * The ESCAPE clause for the LIKE operator allows only expressions that evaluate to a constant at execution time, but aggregrate functions were not being rejected. (Bug #59149) * Memory leaks detected by Valgrind, some of which could cause incorrect query results, were corrected. (Bug #59110, Bug #11766075) mysqlslap failed to check for a NULL return from mysql_store_result() and crashed trying to process the result set. (Bug #59109) * In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could cause a server crash. (Bug #58371) * When mysqldadmin was run with the --sleep and --count options, it went into an infinite loop executing the specified command. (Bug #58221) * Some string manipulating SQL functions use a shared string object intended to contain an immutable empty string. This object was used by the SQL function SUBSTRING_INDEX() to return an empty string when one argument was of the wrong datatype. If the string object was then modified by the SQL function INSERT(), undefined behavior ensued. (Bug #58165, Bug #11765225) * Parsing nested regular expressions could lead to recursion resulting in a stack overflow crash. (Bug #58026, Bug #11765099) * The mysql client went into an infinite loop if the standard input was a directory. (Bug #57450) * The expression const1 BETWEEN const2 AND field was optimized incorrectly and produced incorrect results. (Bug #57030, Bug #11764215) * Some RPM installation scripts used a hardcoded value for the data directory, which could result in a failed installation for users who have a nonstandard data directory location. The same was true for other configuration values such as the PID file name. (Bug #56581, Bug #11763817) * On FreeBSD and OpenBSD, the server incorrectly checked the range of the system date, causing legal values to be rejected. (Bug #55755, Bug #11763089) * When using ExtractValue() or UpdateXML(), if the XML to be read contained an incomplete XML comment, MySQL read beyond the end of the XML string when processing, leading to a crash of the server. (Bug #44332)
2011-03-08 15:06:43 +01:00
share/mysql-test/include/restart_slave_sql.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/rowid_order.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/rpl_change_topology.inc
share/mysql-test/include/rpl_connect.inc
share/mysql-test/include/rpl_connection.inc
Update MySQL package to 5.1.56. Functionality added or changed: * mysqldump --xml now displays comments from column definitions. (Bug #13618) Bugs fixed: * InnoDB Storage Engine: InnoDB returned values for ¡Èrows examined¡É in the query plan that were higher than expected. NULL values were treated in an inconsistent way. The inaccurate statistics could trigger ¡Èfalse positives¡É in combination with the MAX_JOIN_SIZE setting, because the queries did not really examine as many rows as reported. (Bug #30423) * Partitioning: Trying to use the same column more than once in the partitioning key when partitioning a table by KEY caused mysqld to crash. Such duplication of key columns is now expressly disallowed, and fails with an appropriate error. (Bug #53354, Bug #57924) * Replication: When using the statement-based logging format, INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements affecting transactional tables that did not fail were not written to the binary log if they did not insert any rows. (With statement-based logging, all successful statements should be logged, whether they do or do not cause any rows to be changed.) (Bug #59338) * Replication: Formerly, STOP SLAVE stopped the slave I/O thread first and then stopped the slave SQL thread; thus, it was possible for the I/O thread to stop after replicating only part of a transaction which the SQL thread was executing, in wich case¡½if the transaction could not be rolled back safely¡½the SQL thread could hang. Now, STOP SLAVE stops the slave SQL thread first and then stops the I/O thread; this guarantees that the I/O thread can fetch any remaining events in the transaction that the SQL thread is executing, so that the SQL thread can finish the transaction if it cannot be rolled back safely. (Bug #58546) * A query of the following form returned an incorrect result, where the values for col_name in the result set were entirely replaced with NULL values: SELECT DISTINCT col_name ... ORDER BY col_name DESC; (Bug #59308, Bug #11766241) * DELETE or UPDATE statements could fail if they used DATE or DATETIME values with a year, month, or day part of zero. (Bug #59173) * The ESCAPE clause for the LIKE operator allows only expressions that evaluate to a constant at execution time, but aggregrate functions were not being rejected. (Bug #59149) * Memory leaks detected by Valgrind, some of which could cause incorrect query results, were corrected. (Bug #59110, Bug #11766075) mysqlslap failed to check for a NULL return from mysql_store_result() and crashed trying to process the result set. (Bug #59109) * In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could cause a server crash. (Bug #58371) * When mysqldadmin was run with the --sleep and --count options, it went into an infinite loop executing the specified command. (Bug #58221) * Some string manipulating SQL functions use a shared string object intended to contain an immutable empty string. This object was used by the SQL function SUBSTRING_INDEX() to return an empty string when one argument was of the wrong datatype. If the string object was then modified by the SQL function INSERT(), undefined behavior ensued. (Bug #58165, Bug #11765225) * Parsing nested regular expressions could lead to recursion resulting in a stack overflow crash. (Bug #58026, Bug #11765099) * The mysql client went into an infinite loop if the standard input was a directory. (Bug #57450) * The expression const1 BETWEEN const2 AND field was optimized incorrectly and produced incorrect results. (Bug #57030, Bug #11764215) * Some RPM installation scripts used a hardcoded value for the data directory, which could result in a failed installation for users who have a nonstandard data directory location. The same was true for other configuration values such as the PID file name. (Bug #56581, Bug #11763817) * On FreeBSD and OpenBSD, the server incorrectly checked the range of the system date, causing legal values to be rejected. (Bug #55755, Bug #11763089) * When using ExtractValue() or UpdateXML(), if the XML to be read contained an incomplete XML comment, MySQL read beyond the end of the XML string when processing, leading to a crash of the server. (Bug #44332)
2011-03-08 15:06:43 +01:00
share/mysql-test/include/rpl_connection_master.inc
share/mysql-test/include/rpl_connection_slave.inc
share/mysql-test/include/rpl_connection_slave1.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/rpl_diff.inc
share/mysql-test/include/rpl_end.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/rpl_events.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/rpl_for_each_slave.inc
share/mysql-test/include/rpl_generate_sync_chain.inc
share/mysql-test/include/rpl_init.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/rpl_loaddata_charset.inc
share/mysql-test/include/rpl_multi_engine.inc
share/mysql-test/include/rpl_multi_engine2.inc
share/mysql-test/include/rpl_multi_engine3.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/rpl_reconnect.inc
share/mysql-test/include/rpl_reset.inc
share/mysql-test/include/rpl_restart_server.inc
share/mysql-test/include/rpl_start_server.inc
share/mysql-test/include/rpl_start_slaves.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/rpl_stmt_seq.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/rpl_stop_server.inc
share/mysql-test/include/rpl_stop_slaves.inc
share/mysql-test/include/rpl_sync.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/rpl_udf.inc
share/mysql-test/include/running_event_scheduler.inc
share/mysql-test/include/safe_set_to_maybe_ro_var.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/save_master_pos.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/select_ndb_apply_status.inc
share/mysql-test/include/set_binlog_format_mixed.sql
share/mysql-test/include/set_binlog_format_row.sql
share/mysql-test/include/set_binlog_format_statement.sql
share/mysql-test/include/setup_fake_relay_log.inc
share/mysql-test/include/show_binary_logs.inc
share/mysql-test/include/show_binlog_events.inc
share/mysql-test/include/show_binlog_events2.inc
share/mysql-test/include/show_binlog_using_logname.inc
share/mysql-test/include/show_master_logs.inc
share/mysql-test/include/show_master_status.inc
share/mysql-test/include/show_msg.inc
share/mysql-test/include/show_msg80.inc
share/mysql-test/include/show_rpl_debug_info.inc
share/mysql-test/include/show_slave_status.inc
share/mysql-test/include/sp-vars.inc
share/mysql-test/include/start_slave.inc
share/mysql-test/include/stop_slave.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/stop_slave_io.inc
share/mysql-test/include/stop_slave_sql.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/strict_autoinc.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/sync_io_with_master.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/sync_slave_io_with_master.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/sync_slave_sql_with_io.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/system_db_struct.inc
share/mysql-test/include/test_fieldsize.inc
share/mysql-test/include/test_outfile.inc
share/mysql-test/include/testdb_only.inc
share/mysql-test/include/tpcb.inc
share/mysql-test/include/tpcb_disk_data.inc
share/mysql-test/include/truncate_file.inc
share/mysql-test/include/unsafe_binlog.inc
share/mysql-test/include/uses_vardir.inc
share/mysql-test/include/varchar.inc
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/include/view_alias.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/wait_condition.inc
share/mysql-test/include/wait_condition_sp.inc
share/mysql-test/include/wait_for_binlog_event.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/wait_for_query_to_fail.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/include/wait_for_query_to_succeed.inc
share/mysql-test/include/wait_for_slave_io_error.inc
share/mysql-test/include/wait_for_slave_io_to_start.inc
share/mysql-test/include/wait_for_slave_io_to_stop.inc
share/mysql-test/include/wait_for_slave_param.inc
share/mysql-test/include/wait_for_slave_sql_error.inc
share/mysql-test/include/wait_for_slave_sql_error_and_skip.inc
share/mysql-test/include/wait_for_slave_sql_to_start.inc
share/mysql-test/include/wait_for_slave_sql_to_stop.inc
share/mysql-test/include/wait_for_slave_to_start.inc
share/mysql-test/include/wait_for_slave_to_stop.inc
share/mysql-test/include/wait_for_status_var.inc
share/mysql-test/include/wait_show_condition.inc
share/mysql-test/include/wait_until_connected_again.inc
share/mysql-test/include/wait_until_count_sessions.inc
share/mysql-test/include/wait_until_disconnected.inc
share/mysql-test/include/wait_until_rows_count.inc
share/mysql-test/include/windows.inc
share/mysql-test/include/windows_sys_vars.inc
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/include/write_var_to_file.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/lib/My/Config.pm
share/mysql-test/lib/My/ConfigFactory.pm
share/mysql-test/lib/My/CoreDump.pm
share/mysql-test/lib/My/File/Path.pm
share/mysql-test/lib/My/Find.pm
share/mysql-test/lib/My/Handles.pm
share/mysql-test/lib/My/Options.pm
share/mysql-test/lib/My/Platform.pm
share/mysql-test/lib/My/SafeProcess.pm
share/mysql-test/lib/My/SafeProcess/Base.pm
share/mysql-test/lib/My/SysInfo.pm
share/mysql-test/lib/My/Test.pm
share/mysql-test/lib/mtr_cases.pm
share/mysql-test/lib/mtr_gcov.pl
share/mysql-test/lib/mtr_gprof.pl
share/mysql-test/lib/mtr_io.pl
share/mysql-test/lib/mtr_match.pm
share/mysql-test/lib/mtr_misc.pl
share/mysql-test/lib/mtr_process.pl
share/mysql-test/lib/mtr_report.pm
share/mysql-test/lib/mtr_stress.pl
share/mysql-test/lib/mtr_unique.pm
share/mysql-test/lib/v1/My/Config.pm
share/mysql-test/lib/v1/mtr_cases.pl
share/mysql-test/lib/v1/mtr_gcov.pl
share/mysql-test/lib/v1/mtr_gprof.pl
share/mysql-test/lib/v1/mtr_im.pl
share/mysql-test/lib/v1/mtr_io.pl
share/mysql-test/lib/v1/mtr_match.pl
share/mysql-test/lib/v1/mtr_misc.pl
share/mysql-test/lib/v1/mtr_process.pl
share/mysql-test/lib/v1/mtr_report.pl
share/mysql-test/lib/v1/mtr_stress.pl
share/mysql-test/lib/v1/mtr_timer.pl
share/mysql-test/lib/v1/mtr_unique.pl
share/mysql-test/lib/v1/mysql-test-run.pl
share/mysql-test/lib/v1/ndb_config_1_node.ini
share/mysql-test/lib/v1/ndb_config_2_node.ini
share/mysql-test/mtr
share/mysql-test/mysql-stress-test.pl
share/mysql-test/mysql-test-run
share/mysql-test/mysql-test-run.pl
share/mysql-test/r/1st.result
share/mysql-test/r/alias.result
share/mysql-test/r/almost_full.result
share/mysql-test/r/alter_table-big.result
share/mysql-test/r/alter_table.result
share/mysql-test/r/analyse.result
share/mysql-test/r/analyze.result
share/mysql-test/r/ansi.result
share/mysql-test/r/archive-big.result
share/mysql-test/r/archive.result
share/mysql-test/r/archive_bitfield.result
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/r/archive_debug.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/archive_gis.result
share/mysql-test/r/auto_increment.result
share/mysql-test/r/backup.result
share/mysql-test/r/bench_count_distinct.result
share/mysql-test/r/big_test.require
share/mysql-test/r/bigint.result
share/mysql-test/r/binary.result
share/mysql-test/r/binlog_tx_isolation.result
share/mysql-test/r/bool.result
share/mysql-test/r/bootstrap.result
Update mysql51-client/mysql51-server package to 5.1.45. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html Added a patch for recent security problem to mysql51-server, too. http://secunia.com/advisories/39454
2010-04-21 00:58:10 +02:00
share/mysql-test/r/bug39022.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/bug46080.result
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/r/bug46261.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/bug46760.result
share/mysql-test/r/bug47671.result
share/mysql-test/r/bulk_replace.result
share/mysql-test/r/cache_innodb.result
share/mysql-test/r/case.result
share/mysql-test/r/case_insensitive_file_system.require
share/mysql-test/r/case_insensitive_fs.require
share/mysql-test/r/case_sensitive_file_system.require
share/mysql-test/r/cast.result
share/mysql-test/r/change_user.result
share/mysql-test/r/check.result
share/mysql-test/r/check_var_limit.require
share/mysql-test/r/client_xml.result
share/mysql-test/r/comments.result
share/mysql-test/r/commit_1innodb.result
share/mysql-test/r/compare.result
share/mysql-test/r/compress.result
share/mysql-test/r/concurrent_innodb_safelog.result
share/mysql-test/r/concurrent_innodb_unsafelog.result
share/mysql-test/r/connect.result
share/mysql-test/r/consistent_snapshot.result
share/mysql-test/r/constraints.result
share/mysql-test/r/contributors.result
share/mysql-test/r/count_distinct.result
share/mysql-test/r/count_distinct2.result
share/mysql-test/r/count_distinct3.result
share/mysql-test/r/crash_commit_before.result
share/mysql-test/r/create-big.result
share/mysql-test/r/create.result
share/mysql-test/r/create_not_windows.result
share/mysql-test/r/create_select_tmp.result
share/mysql-test/r/csv.result
share/mysql-test/r/csv_alter_table.result
share/mysql-test/r/csv_not_null.result
share/mysql-test/r/ctype_ascii.result
share/mysql-test/r/ctype_big5.result
share/mysql-test/r/ctype_collate.result
share/mysql-test/r/ctype_cp1250_ch.result
share/mysql-test/r/ctype_cp1251.result
share/mysql-test/r/ctype_cp932_binlog_row.result
share/mysql-test/r/ctype_cp932_binlog_stm.result
share/mysql-test/r/ctype_create.result
share/mysql-test/r/ctype_eucjpms.result
share/mysql-test/r/ctype_euckr.result
share/mysql-test/r/ctype_filename.result
share/mysql-test/r/ctype_filesystem.result
share/mysql-test/r/ctype_gb2312.result
share/mysql-test/r/ctype_gbk.result
share/mysql-test/r/ctype_gbk_binlog.result
share/mysql-test/r/ctype_hebrew.result
share/mysql-test/r/ctype_latin1.result
share/mysql-test/r/ctype_latin1_de.result
share/mysql-test/r/ctype_latin2.result
share/mysql-test/r/ctype_latin2_ch.result
share/mysql-test/r/ctype_ldml.result
share/mysql-test/r/ctype_many.result
share/mysql-test/r/ctype_mb.result
share/mysql-test/r/ctype_recoding.result
share/mysql-test/r/ctype_sjis.result
share/mysql-test/r/ctype_tis620.result
share/mysql-test/r/ctype_uca.result
share/mysql-test/r/ctype_ucs.result
share/mysql-test/r/ctype_ucs2_def.result
share/mysql-test/r/ctype_ujis.result
share/mysql-test/r/ctype_ujis_ucs2.result
share/mysql-test/r/ctype_utf8.result
share/mysql-test/r/date_formats.result
share/mysql-test/r/ddl_i18n_koi8r.result
share/mysql-test/r/ddl_i18n_utf8.result
share/mysql-test/r/deadlock_innodb.result
share/mysql-test/r/debug_sync.result
share/mysql-test/r/default.result
share/mysql-test/r/delayed.result
share/mysql-test/r/delete.result
share/mysql-test/r/derived.result
share/mysql-test/r/dirty_close.result
share/mysql-test/r/disabled_partition.require
share/mysql-test/r/distinct.result
share/mysql-test/r/drop.result
share/mysql-test/r/empty_table.result
share/mysql-test/r/endspace.result
share/mysql-test/r/error_simulation.result
share/mysql-test/r/errors.result
share/mysql-test/r/events_1.result
share/mysql-test/r/events_2.result
share/mysql-test/r/events_bugs.result
share/mysql-test/r/events_embedded.result
share/mysql-test/r/events_grant.result
share/mysql-test/r/events_logs_tests.result
share/mysql-test/r/events_microsec.result
share/mysql-test/r/events_restart.result
share/mysql-test/r/events_scheduling.result
share/mysql-test/r/events_stress.result
share/mysql-test/r/events_time_zone.result
share/mysql-test/r/events_trans.result
share/mysql-test/r/events_trans_notembedded.result
share/mysql-test/r/exampledb.result
share/mysql-test/r/execution_constants.result
share/mysql-test/r/explain.result
share/mysql-test/r/fix_priv_tables.result
share/mysql-test/r/flush.result
share/mysql-test/r/flush2.result
share/mysql-test/r/flush_block_commit.result
share/mysql-test/r/flush_block_commit_notembedded.result
share/mysql-test/r/flush_read_lock_kill.result
share/mysql-test/r/flush_table.result
share/mysql-test/r/foreign_key.result
share/mysql-test/r/fulltext.result
share/mysql-test/r/fulltext2.result
share/mysql-test/r/fulltext3.result
share/mysql-test/r/fulltext_cache.result
share/mysql-test/r/fulltext_distinct.result
share/mysql-test/r/fulltext_left_join.result
share/mysql-test/r/fulltext_multi.result
share/mysql-test/r/fulltext_order_by.result
share/mysql-test/r/fulltext_plugin.result
share/mysql-test/r/fulltext_update.result
share/mysql-test/r/fulltext_var.result
share/mysql-test/r/func_compress.result
share/mysql-test/r/func_concat.result
share/mysql-test/r/func_crypt.result
share/mysql-test/r/func_date_add.result
share/mysql-test/r/func_default.result
share/mysql-test/r/func_des_encrypt.result
share/mysql-test/r/func_encrypt.result
share/mysql-test/r/func_encrypt_nossl.result
Update mysql51-{client,server} package to 5.1.57. This is simply maintenance release, no security fix. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-57.html in detail.
2011-05-08 18:01:57 +02:00
share/mysql-test/r/func_encrypt_ucs2.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/func_equal.result
share/mysql-test/r/func_gconcat.result
share/mysql-test/r/func_group.result
share/mysql-test/r/func_group_innodb.result
share/mysql-test/r/func_if.result
share/mysql-test/r/func_in.result
share/mysql-test/r/func_isnull.result
share/mysql-test/r/func_like.result
share/mysql-test/r/func_math.result
share/mysql-test/r/func_misc.result
share/mysql-test/r/func_op.result
share/mysql-test/r/func_regexp.result
share/mysql-test/r/func_rollback.result
share/mysql-test/r/func_sapdb.result
share/mysql-test/r/func_set.result
share/mysql-test/r/func_str.result
share/mysql-test/r/func_system.result
share/mysql-test/r/func_test.result
share/mysql-test/r/func_time.result
share/mysql-test/r/func_timestamp.result
share/mysql-test/r/gcc296.result
share/mysql-test/r/gis-rtree.result
share/mysql-test/r/gis.result
share/mysql-test/r/grant.result
share/mysql-test/r/grant2.result
share/mysql-test/r/grant3.result
share/mysql-test/r/grant_cache_no_prot.result
share/mysql-test/r/grant_cache_ps_prot.result
share/mysql-test/r/grant_lowercase_fs.result
share/mysql-test/r/greedy_optimizer.result
share/mysql-test/r/group_by.result
share/mysql-test/r/group_min_max.result
share/mysql-test/r/group_min_max_innodb.result
share/mysql-test/r/handler_innodb.result
share/mysql-test/r/handler_myisam.result
share/mysql-test/r/have_big5.require
share/mysql-test/r/have_binlog_format_mixed.require
share/mysql-test/r/have_binlog_format_row.require
share/mysql-test/r/have_binlog_format_statement.require
share/mysql-test/r/have_community_features.require
share/mysql-test/r/have_compress.require
share/mysql-test/r/have_cp1250_ch.require
share/mysql-test/r/have_cp1251.require
share/mysql-test/r/have_cp866.require
share/mysql-test/r/have_cp932.require
share/mysql-test/r/have_crypt.require
share/mysql-test/r/have_debug.require
share/mysql-test/r/have_debug_sync.require
share/mysql-test/r/have_dynamic_loading.require
share/mysql-test/r/have_eucjpms.require
share/mysql-test/r/have_euckr.require
share/mysql-test/r/have_example_plugin.require
share/mysql-test/r/have_gb2312.require
share/mysql-test/r/have_gbk.require
share/mysql-test/r/have_geometry.require
share/mysql-test/r/have_koi8r.require
share/mysql-test/r/have_latin2_ch.require
share/mysql-test/r/have_local_infile.require
share/mysql-test/r/have_log_bin.require
share/mysql-test/r/have_met_timezone.require
share/mysql-test/r/have_moscow_leap_timezone.require
share/mysql-test/r/have_mysql_upgrade.result
share/mysql-test/r/have_ndb_extra.require
share/mysql-test/r/have_ndbapi_examples.require
share/mysql-test/r/have_outfile.require
share/mysql-test/r/have_partition.require
share/mysql-test/r/have_perror.require
share/mysql-test/r/have_query_cache.require
share/mysql-test/r/have_simple_parser.require
share/mysql-test/r/have_sjis.require
share/mysql-test/r/have_ssl.require
share/mysql-test/r/have_symlink.require
share/mysql-test/r/have_tis620.require
share/mysql-test/r/have_ucs2.require
share/mysql-test/r/have_udf_example.require
share/mysql-test/r/have_ujis.require
share/mysql-test/r/have_utf8.require
share/mysql-test/r/having.result
share/mysql-test/r/heap.result
share/mysql-test/r/heap_auto_increment.result
share/mysql-test/r/heap_btree.result
share/mysql-test/r/heap_hash.result
share/mysql-test/r/help.result
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/r/implicit_char_to_num_conversion.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/index_merge_innodb.result
share/mysql-test/r/index_merge_myisam.result
share/mysql-test/r/information_schema.result
share/mysql-test/r/information_schema_chmod.result
share/mysql-test/r/information_schema_db.result
share/mysql-test/r/information_schema_inno.result
share/mysql-test/r/information_schema_part.result
share/mysql-test/r/init_connect.result
share/mysql-test/r/init_file.result
share/mysql-test/r/innodb_ignore_builtin.result
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/r/innodb_mysql_lock2.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/insert.result
share/mysql-test/r/insert_notembedded.result
share/mysql-test/r/insert_select.result
share/mysql-test/r/insert_update.result
share/mysql-test/r/is_debug_build.require
share/mysql-test/r/is_embedded.require
share/mysql-test/r/isam.result
share/mysql-test/r/join.result
share/mysql-test/r/join_crash.result
share/mysql-test/r/join_nested.result
share/mysql-test/r/join_outer.result
share/mysql-test/r/join_outer_innodb.result
share/mysql-test/r/key.result
share/mysql-test/r/key_cache.result
share/mysql-test/r/key_diff.result
share/mysql-test/r/key_primary.result
share/mysql-test/r/keywords.result
share/mysql-test/r/kill.result
share/mysql-test/r/limit.result
share/mysql-test/r/loaddata.result
share/mysql-test/r/loaddata_autocom_innodb.result
share/mysql-test/r/locale.result
share/mysql-test/r/lock.result
share/mysql-test/r/lock_multi.result
share/mysql-test/r/lock_multi_bug38499.result
share/mysql-test/r/lock_multi_bug38691.result
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/r/lock_sync.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/lock_tables_lost_commit.result
share/mysql-test/r/log_state.result
share/mysql-test/r/log_tables-big.result
share/mysql-test/r/log_tables.result
share/mysql-test/r/log_tables_debug.result
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/r/log_tables_upgrade.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/long_tmpdir.result
share/mysql-test/r/lowercase0.require
share/mysql-test/r/lowercase1.require
share/mysql-test/r/lowercase2.require
share/mysql-test/r/lowercase_fs_off.result
share/mysql-test/r/lowercase_mixed_tmpdir.result
share/mysql-test/r/lowercase_mixed_tmpdir_innodb.result
share/mysql-test/r/lowercase_table.result
share/mysql-test/r/lowercase_table2.result
share/mysql-test/r/lowercase_table3.result
Update mysql51-{client,server} to 5.1.53. Most changes are related to replication and seems to no security fix. For more detail, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html
2010-11-26 14:52:58 +01:00
share/mysql-test/r/lowercase_table4.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/lowercase_table_grant.result
share/mysql-test/r/lowercase_table_qcache.result
share/mysql-test/r/lowercase_utf8.result
share/mysql-test/r/lowercase_view.result
share/mysql-test/r/merge-big.result
share/mysql-test/r/merge.result
share/mysql-test/r/merge_innodb.result
share/mysql-test/r/metadata.result
share/mysql-test/r/mix2_myisam.result
share/mysql-test/r/mix2_myisam_ucs2.result
share/mysql-test/r/multi_statement.result
share/mysql-test/r/multi_update.result
share/mysql-test/r/multi_update2.result
share/mysql-test/r/multi_update_tiny_hash.result
share/mysql-test/r/myisam-blob.result
share/mysql-test/r/myisam-system.result
share/mysql-test/r/myisam.result
share/mysql-test/r/myisam_crash_before_flush_keys.result
share/mysql-test/r/myisam_debug.result
share/mysql-test/r/myisampack.result
share/mysql-test/r/mysql-bug41486.result
share/mysql-test/r/mysql-bug45236.result
share/mysql-test/r/mysql.result
share/mysql-test/r/mysql_client_test.result
share/mysql-test/r/mysql_comments.result
share/mysql-test/r/mysql_cp932.result
share/mysql-test/r/mysql_protocols.result
share/mysql-test/r/mysql_upgrade.result
share/mysql-test/r/mysqladmin.result
share/mysql-test/r/mysqlbinlog.result
share/mysql-test/r/mysqlbinlog_row_big.result
share/mysql-test/r/mysqlcheck.result
share/mysql-test/r/mysqldump-compat.result
share/mysql-test/r/mysqldump-max.result
share/mysql-test/r/mysqldump-no-binlog.result
share/mysql-test/r/mysqldump.result
share/mysql-test/r/mysqldump_restore.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/r/mysqlhotcopy_archive.result
share/mysql-test/r/mysqlhotcopy_myisam.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/mysqlshow.result
share/mysql-test/r/mysqlslap.result
share/mysql-test/r/mysqltest.result
share/mysql-test/r/named_pipe.result
share/mysql-test/r/ndb_default_cluster.require
share/mysql-test/r/negation_elimination.result
share/mysql-test/r/no-threads.result
Update mysql51-client/mysql51-server package to 5.1.45. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html Added a patch for recent security problem to mysql51-server, too. http://secunia.com/advisories/39454
2010-04-21 00:58:10 +02:00
share/mysql-test/r/no_binlog.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/not_embedded.require
share/mysql-test/r/not_embedded_server.result
share/mysql-test/r/not_ndb.require
share/mysql-test/r/not_ndb_default.require
share/mysql-test/r/not_openssl.require
share/mysql-test/r/not_partition.require
share/mysql-test/r/not_partition.result
share/mysql-test/r/not_true.require
share/mysql-test/r/not_valgrind.require
share/mysql-test/r/not_windows.require
share/mysql-test/r/null.result
share/mysql-test/r/null_key.result
share/mysql-test/r/odbc.result
share/mysql-test/r/olap.result
share/mysql-test/r/one_thread_per_connection.require
share/mysql-test/r/openssl_1.result
share/mysql-test/r/order_by.result
share/mysql-test/r/order_fill_sortbuf.result
share/mysql-test/r/outfile.result
share/mysql-test/r/outfile_loaddata.result
share/mysql-test/r/overflow.result
share/mysql-test/r/packet.result
share/mysql-test/r/parser.result
share/mysql-test/r/parser_bug21114_innodb.result
share/mysql-test/r/parser_not_embedded.result
share/mysql-test/r/parser_precedence.result
share/mysql-test/r/parser_stack.result
share/mysql-test/r/partition.result
share/mysql-test/r/partition_archive.result
Update mysql51-{client,server} package from 5.1.51 to 5.1.52. This is maintainous release and pleare refer in detail: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html One note from the changes: * Security Fix: In prepared-statement mode, EXPLAIN for a SELECT from a derived table caused a server crash. (Bug#54488)
2010-11-04 16:57:07 +01:00
share/mysql-test/r/partition_binlog_stmt.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/partition_blackhole.result
share/mysql-test/r/partition_bug18198.result
Update mysql51-{client,server} to 5.1.63 (MySQL 5.1.63). Changes (http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html): * Security Fix: Bug #64884 was fixed. * Security Fix: Bug #59387 was fixed. * InnoDB: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. (Bug #13847885) * InnoDB: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. (Bug #12861864, Bug #11766019) * InnoDB: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. (Bug #11766634, Bug #59783) * Partitioning: After updating a row of a partitioned table and selecting that row within the same transaction with the query cache enabled, then performing a ROLLBACK, the same result was returned by an identical SELECT issued in a new transaction. (Bug #11761296, Bug #53775) * Replication: The --relay-log-space-limit option was sometimes ignored. More specifically, when the SQL thread went to sleep, it allowed the I/O thread to queue additional events in such a way that the relay log space limit was bypassed, and the number of events in the queue could grow well past the point where the relay logs needed to be rotated. Now in such cases, the SQL thread checks to see whether the I/O thread should rotate and provide the SQL thread a chance to purge the logs (thus freeing space). Note that, when the SQL thread is in the middle of a transaction, it cannot purge the logs; it can only ask for more events until the transaction is complete. Once the transaction is finished, the SQL thread can immediately instruct the I/O thread to rotate. (Bug #12400313, Bug #64503) References: See also Bug #13806492. * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored procedures on slave servers could cause replication failures. (Bug #12601974) * If the system time was adjusted backward during query execution, the apparent execution time could be negative. But in some cases these queries would be written to the slow query log, with the negative execution time written as a large unsigned number. Now statements with apparent negative execution time are not written to the slow query log. (Bug #63524, Bug #13454045) References: See also Bug #27208. * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * SHOW statements treated stored procedure, stored function, and event names as case sensitive. (Bug #56224, Bug #11763507) * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 14:59:39 +02:00
share/mysql-test/r/partition_cache.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/partition_charset.result
share/mysql-test/r/partition_csv.result
share/mysql-test/r/partition_datatype.result
Update mysql51-client/mysql51-server package to 5.1.45. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html Added a patch for recent security problem to mysql51-server, too. http://secunia.com/advisories/39454
2010-04-21 00:58:10 +02:00
share/mysql-test/r/partition_debug_sync.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/partition_disabled.result
share/mysql-test/r/partition_error.result
share/mysql-test/r/partition_federated.result
share/mysql-test/r/partition_grant.result
share/mysql-test/r/partition_hash.result
share/mysql-test/r/partition_innodb.result
share/mysql-test/r/partition_innodb_builtin.result
share/mysql-test/r/partition_innodb_plugin.result
share/mysql-test/r/partition_innodb_semi_consistent.result
share/mysql-test/r/partition_innodb_stmt.result
share/mysql-test/r/partition_list.result
share/mysql-test/r/partition_mgm.result
share/mysql-test/r/partition_mgm_err.result
share/mysql-test/r/partition_mgm_err2.result
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/r/partition_myisam.result
Update mysql51-{client,server} package to 5.1.51, MySQL 5.1.51. For full changes, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html Here is summary for security fixes: * Security Fix: During evaluation of arguments to extreme-value functions (such as LEAST() and GREATEST()), type errors did not propagate properly, causing the server to crash. (Bug#55826) * Security Fix: The server could crash after materializing a derived table that required a temporary table for grouping. (Bug#55568) * Security Fix: A user-variable assignment expression that is evaluated in a logical expression context can be precalculated in a temporary table for GROUP BY. However, when the expression value is used after creation of the temporary table, it was re-evaluated, not read from the table and a server crash resulted. (Bug#55564) * Security Fix: Pre-evaluation of LIKE predicates during view preparation could cause a server crash. (Bug#54568) * Security Fix: GROUP_CONCAT() and WITH ROLLUP together could cause a server crash. (Bug#54476) * Security Fix: Queries could cause a server crash if the GREATEST() or LEAST() function had a mixed list of numeric and LONGBLOB arguments, and the result of such a function was processed using an intermediate temporary table. (Bug#54461) * Security Fix: Queries with nested joins could cause an infinite loop in the server when used from stored procedures and prepared statements. (Bug#53544) * Security Fix: The PolyFromWKB() function could crash the server when improper WKB data was passed to the function. (Bug#51875)
2010-10-06 14:37:58 +02:00
share/mysql-test/r/partition_not_blackhole.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/partition_not_windows.result
share/mysql-test/r/partition_open_files_limit.result
share/mysql-test/r/partition_order.result
share/mysql-test/r/partition_pruning.result
share/mysql-test/r/partition_range.result
share/mysql-test/r/partition_rename_longfilename.result
share/mysql-test/r/partition_symlink.result
share/mysql-test/r/partition_windows.result
share/mysql-test/r/perror-win.result
share/mysql-test/r/perror.result
share/mysql-test/r/plugin.result
share/mysql-test/r/plugin_load.result
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/r/plugin_not_embedded.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/preload.result
share/mysql-test/r/profiling.result
share/mysql-test/r/ps.result
share/mysql-test/r/ps_10nestset.result
share/mysql-test/r/ps_11bugs.result
share/mysql-test/r/ps_1general.result
share/mysql-test/r/ps_2myisam.result
share/mysql-test/r/ps_3innodb.result
share/mysql-test/r/ps_4heap.result
share/mysql-test/r/ps_5merge.result
share/mysql-test/r/ps_ddl.result
share/mysql-test/r/ps_ddl1.result
share/mysql-test/r/ps_grant.result
share/mysql-test/r/ps_not_windows.result
share/mysql-test/r/query_cache.result
share/mysql-test/r/query_cache_28249.result
share/mysql-test/r/query_cache_debug.result
share/mysql-test/r/query_cache_merge.result
share/mysql-test/r/query_cache_notembedded.result
share/mysql-test/r/query_cache_ps_no_prot.result
share/mysql-test/r/query_cache_ps_ps_prot.result
share/mysql-test/r/query_cache_with_views.result
share/mysql-test/r/raid.result
share/mysql-test/r/range.result
share/mysql-test/r/read_many_rows_innodb.result
share/mysql-test/r/read_only.result
share/mysql-test/r/read_only_innodb.result
share/mysql-test/r/rename.result
share/mysql-test/r/renamedb.result
share/mysql-test/r/repair.result
share/mysql-test/r/replace.result
share/mysql-test/r/rollback.result
share/mysql-test/r/round.result
share/mysql-test/r/row.result
share/mysql-test/r/rowid_order_innodb.result
share/mysql-test/r/rpl_colSize.result
share/mysql-test/r/rpl_extraColmaster_innodb.result
share/mysql-test/r/rpl_extraColmaster_myisam.result
share/mysql-test/r/schema.result
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/r/secure_file_priv_win.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/select.result
share/mysql-test/r/select_found.result
share/mysql-test/r/select_safe.result
share/mysql-test/r/server_id.require
share/mysql-test/r/server_id1.require
share/mysql-test/r/shm.result
share/mysql-test/r/show_check.result
share/mysql-test/r/skip_grants.result
share/mysql-test/r/skip_log_bin.result
share/mysql-test/r/skip_name_resolve.result
share/mysql-test/r/slave-running.result
share/mysql-test/r/slave-stopped.result
share/mysql-test/r/sp-big.result
share/mysql-test/r/sp-bugs.result
share/mysql-test/r/sp-code.result
share/mysql-test/r/sp-destruct.result
share/mysql-test/r/sp-dynamic.result
share/mysql-test/r/sp-error.result
share/mysql-test/r/sp-fib.result
share/mysql-test/r/sp-prelocking.result
share/mysql-test/r/sp-security.result
share/mysql-test/r/sp-threads.result
share/mysql-test/r/sp-ucs2.result
share/mysql-test/r/sp-vars.result
share/mysql-test/r/sp.result
share/mysql-test/r/sp_gis.result
share/mysql-test/r/sp_notembedded.result
share/mysql-test/r/sp_stress_case.result
share/mysql-test/r/sp_sync.result
share/mysql-test/r/sp_trans.result
share/mysql-test/r/sp_trans_log.result
share/mysql-test/r/sql_mode.result
share/mysql-test/r/ssl-big.result
share/mysql-test/r/ssl.result
share/mysql-test/r/ssl_8k_key.result
Update mysql51-{client,server} package to 5.1.57. This is simply maintenance release, no security fix. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-57.html in detail.
2011-05-08 18:01:57 +02:00
share/mysql-test/r/ssl_cipher.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/ssl_compress.result
share/mysql-test/r/ssl_connect.result
share/mysql-test/r/status.result
share/mysql-test/r/status2.result
share/mysql-test/r/strict.result
share/mysql-test/r/strict_autoinc_1myisam.result
share/mysql-test/r/strict_autoinc_2innodb.result
share/mysql-test/r/strict_autoinc_3heap.result
share/mysql-test/r/subselect.result
share/mysql-test/r/subselect2.result
share/mysql-test/r/subselect3.result
share/mysql-test/r/subselect4.result
share/mysql-test/r/subselect_debug.result
share/mysql-test/r/subselect_gis.result
share/mysql-test/r/subselect_innodb.result
share/mysql-test/r/subselect_notembedded.result
share/mysql-test/r/sum_distinct-big.result
share/mysql-test/r/sum_distinct.result
share/mysql-test/r/symlink.result
share/mysql-test/r/synchronization.result
share/mysql-test/r/sysdate_is_now.result
share/mysql-test/r/system_mysql_db.result
share/mysql-test/r/system_mysql_db_refs.result
share/mysql-test/r/tablelock.result
share/mysql-test/r/temp_table.result
share/mysql-test/r/testdb_only.require
share/mysql-test/r/timezone.result
share/mysql-test/r/timezone2.result
share/mysql-test/r/timezone3.result
share/mysql-test/r/timezone4.result
share/mysql-test/r/timezone_grant.result
share/mysql-test/r/trigger-compat.result
share/mysql-test/r/trigger-trans.result
share/mysql-test/r/trigger.result
share/mysql-test/r/trigger_notembedded.result
share/mysql-test/r/true.require
share/mysql-test/r/truncate.result
share/mysql-test/r/type_binary.result
share/mysql-test/r/type_bit.result
share/mysql-test/r/type_bit_innodb.result
share/mysql-test/r/type_blob.result
share/mysql-test/r/type_date.result
share/mysql-test/r/type_datetime.result
share/mysql-test/r/type_decimal.result
share/mysql-test/r/type_enum.result
share/mysql-test/r/type_float.result
share/mysql-test/r/type_nchar.result
share/mysql-test/r/type_newdecimal-big.result
share/mysql-test/r/type_newdecimal.result
share/mysql-test/r/type_ranges.result
share/mysql-test/r/type_set.result
share/mysql-test/r/type_time.result
share/mysql-test/r/type_timestamp.result
share/mysql-test/r/type_uint.result
share/mysql-test/r/type_varchar.result
share/mysql-test/r/type_year.result
share/mysql-test/r/udf.result
share/mysql-test/r/udf_skip_grants.result
share/mysql-test/r/union.result
share/mysql-test/r/unsafe_binlog_innodb.result
share/mysql-test/r/update.result
share/mysql-test/r/upgrade.result
share/mysql-test/r/user_limits.result
share/mysql-test/r/user_var-binlog.result
share/mysql-test/r/user_var.result
share/mysql-test/r/varbinary.result
share/mysql-test/r/variables-big.result
share/mysql-test/r/variables-notembedded.result
share/mysql-test/r/variables.result
Update mysql51-client/mysql51-server package to 5.1.45. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html Added a patch for recent security problem to mysql51-server, too. http://secunia.com/advisories/39454
2010-04-21 00:58:10 +02:00
share/mysql-test/r/variables_community.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/variables_debug.result
share/mysql-test/r/view.result
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/r/view_alias.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/r/view_grant.result
share/mysql-test/r/wait_timeout.result
share/mysql-test/r/warnings.result
share/mysql-test/r/warnings_engine_disabled.result
share/mysql-test/r/windows.require
share/mysql-test/r/windows.result
share/mysql-test/r/xa.result
share/mysql-test/r/xml.result
share/mysql-test/std_data/14897.frm
share/mysql-test/std_data/Index.xml
share/mysql-test/std_data/Moscow_leap
share/mysql-test/std_data/bad_gis_data.dat
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/std_data/binlog_savepoint.000001
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/std_data/binlog_transaction.000001
share/mysql-test/std_data/bug15328.cnf
share/mysql-test/std_data/bug16266.000001
share/mysql-test/std_data/bug19371.MYD
share/mysql-test/std_data/bug19371.MYI
share/mysql-test/std_data/bug19371.frm
share/mysql-test/std_data/bug30435_10k_items.txt
share/mysql-test/std_data/bug30435_5k.txt
share/mysql-test/std_data/bug33029-slave-relay-bin.000001
share/mysql-test/std_data/bug35469.dat
share/mysql-test/std_data/bug36055.MYD
share/mysql-test/std_data/bug36055.MYI
share/mysql-test/std_data/bug36055.frm
share/mysql-test/std_data/bug37631.MYD
share/mysql-test/std_data/bug37631.MYI
share/mysql-test/std_data/bug37631.frm
share/mysql-test/std_data/bug40482-bin.000001
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/std_data/bug46565.ARZ
share/mysql-test/std_data/bug46565.frm
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/std_data/bug47012.ARM
share/mysql-test/std_data/bug47012.ARZ
share/mysql-test/std_data/bug47012.frm
share/mysql-test/std_data/bug47142_master-bin.000001
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/std_data/bug48265.frm
Update mysql51-client/mysql51-server package to 5.1.45. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html Added a patch for recent security problem to mysql51-server, too. http://secunia.com/advisories/39454
2010-04-21 00:58:10 +02:00
share/mysql-test/std_data/bug48449.frm
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/std_data/bug49823.CSM
share/mysql-test/std_data/bug49823.CSV
share/mysql-test/std_data/bug49823.frm
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/std_data/cacert.pem
share/mysql-test/std_data/charset_utf8.txt
Update MySQL package to 5.1.56. Functionality added or changed: * mysqldump --xml now displays comments from column definitions. (Bug #13618) Bugs fixed: * InnoDB Storage Engine: InnoDB returned values for ¡Èrows examined¡É in the query plan that were higher than expected. NULL values were treated in an inconsistent way. The inaccurate statistics could trigger ¡Èfalse positives¡É in combination with the MAX_JOIN_SIZE setting, because the queries did not really examine as many rows as reported. (Bug #30423) * Partitioning: Trying to use the same column more than once in the partitioning key when partitioning a table by KEY caused mysqld to crash. Such duplication of key columns is now expressly disallowed, and fails with an appropriate error. (Bug #53354, Bug #57924) * Replication: When using the statement-based logging format, INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements affecting transactional tables that did not fail were not written to the binary log if they did not insert any rows. (With statement-based logging, all successful statements should be logged, whether they do or do not cause any rows to be changed.) (Bug #59338) * Replication: Formerly, STOP SLAVE stopped the slave I/O thread first and then stopped the slave SQL thread; thus, it was possible for the I/O thread to stop after replicating only part of a transaction which the SQL thread was executing, in wich case¡½if the transaction could not be rolled back safely¡½the SQL thread could hang. Now, STOP SLAVE stops the slave SQL thread first and then stops the I/O thread; this guarantees that the I/O thread can fetch any remaining events in the transaction that the SQL thread is executing, so that the SQL thread can finish the transaction if it cannot be rolled back safely. (Bug #58546) * A query of the following form returned an incorrect result, where the values for col_name in the result set were entirely replaced with NULL values: SELECT DISTINCT col_name ... ORDER BY col_name DESC; (Bug #59308, Bug #11766241) * DELETE or UPDATE statements could fail if they used DATE or DATETIME values with a year, month, or day part of zero. (Bug #59173) * The ESCAPE clause for the LIKE operator allows only expressions that evaluate to a constant at execution time, but aggregrate functions were not being rejected. (Bug #59149) * Memory leaks detected by Valgrind, some of which could cause incorrect query results, were corrected. (Bug #59110, Bug #11766075) mysqlslap failed to check for a NULL return from mysql_store_result() and crashed trying to process the result set. (Bug #59109) * In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could cause a server crash. (Bug #58371) * When mysqldadmin was run with the --sleep and --count options, it went into an infinite loop executing the specified command. (Bug #58221) * Some string manipulating SQL functions use a shared string object intended to contain an immutable empty string. This object was used by the SQL function SUBSTRING_INDEX() to return an empty string when one argument was of the wrong datatype. If the string object was then modified by the SQL function INSERT(), undefined behavior ensued. (Bug #58165, Bug #11765225) * Parsing nested regular expressions could lead to recursion resulting in a stack overflow crash. (Bug #58026, Bug #11765099) * The mysql client went into an infinite loop if the standard input was a directory. (Bug #57450) * The expression const1 BETWEEN const2 AND field was optimized incorrectly and produced incorrect results. (Bug #57030, Bug #11764215) * Some RPM installation scripts used a hardcoded value for the data directory, which could result in a failed installation for users who have a nonstandard data directory location. The same was true for other configuration values such as the PID file name. (Bug #56581, Bug #11763817) * On FreeBSD and OpenBSD, the server incorrectly checked the range of the system date, causing legal values to be rejected. (Bug #55755, Bug #11763089) * When using ExtractValue() or UpdateXML(), if the XML to be read contained an incomplete XML comment, MySQL read beyond the end of the XML string when processing, leading to a crash of the server. (Bug #44332)
2011-03-08 15:06:43 +01:00
share/mysql-test/std_data/checkDBI_DBD-mysql.pl
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/std_data/client-cert.pem
share/mysql-test/std_data/client-key.pem
share/mysql-test/std_data/corrupt-relay-bin.000624
share/mysql-test/std_data/corrupt_t1#P#p1.MYI
share/mysql-test/std_data/corrupt_t1.MYI
share/mysql-test/std_data/des_key_file
share/mysql-test/std_data/funcs_1/innodb_tb1.txt
share/mysql-test/std_data/funcs_1/innodb_tb2.txt
share/mysql-test/std_data/funcs_1/innodb_tb3.txt
share/mysql-test/std_data/funcs_1/innodb_tb4.txt
share/mysql-test/std_data/funcs_1/load_file.txt
share/mysql-test/std_data/funcs_1/memory_tb1.txt
share/mysql-test/std_data/funcs_1/memory_tb2.txt
share/mysql-test/std_data/funcs_1/memory_tb3.txt
share/mysql-test/std_data/funcs_1/memory_tb4.txt
share/mysql-test/std_data/funcs_1/myisam_tb1.txt
share/mysql-test/std_data/funcs_1/myisam_tb2.txt
share/mysql-test/std_data/funcs_1/myisam_tb3.txt
share/mysql-test/std_data/funcs_1/myisam_tb4.txt
share/mysql-test/std_data/funcs_1/ndb_tb1.txt
share/mysql-test/std_data/funcs_1/ndb_tb2.txt
share/mysql-test/std_data/funcs_1/ndb_tb3.txt
share/mysql-test/std_data/funcs_1/ndb_tb4.txt
share/mysql-test/std_data/funcs_1/t3.txt
share/mysql-test/std_data/funcs_1/t4.txt
share/mysql-test/std_data/funcs_1/t7.txt
share/mysql-test/std_data/funcs_1/t9.txt
share/mysql-test/std_data/init_file.dat
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/std_data/intersect-bug50389.tsv
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/std_data/latin1.xml
share/mysql-test/std_data/loaddata1.dat
share/mysql-test/std_data/loaddata2.dat
share/mysql-test/std_data/loaddata3.dat
share/mysql-test/std_data/loaddata4.dat
share/mysql-test/std_data/loaddata5.dat
share/mysql-test/std_data/loaddata6.dat
share/mysql-test/std_data/loaddata_dq.dat
share/mysql-test/std_data/loaddata_pair.dat
share/mysql-test/std_data/loaddata_utf8.dat
share/mysql-test/std_data/master-bin.000001
share/mysql-test/std_data/ndb_backup50/BACKUP-1-0.1.Data
share/mysql-test/std_data/ndb_backup50/BACKUP-1-0.2.Data
share/mysql-test/std_data/ndb_backup50/BACKUP-1.1.ctl
share/mysql-test/std_data/ndb_backup50/BACKUP-1.1.log
share/mysql-test/std_data/ndb_backup50/BACKUP-1.2.ctl
share/mysql-test/std_data/ndb_backup50/BACKUP-1.2.log
share/mysql-test/std_data/ndb_backup50/BACKUP-2-0.1.Data
share/mysql-test/std_data/ndb_backup50/BACKUP-2-0.2.Data
share/mysql-test/std_data/ndb_backup50/BACKUP-2.1.ctl
share/mysql-test/std_data/ndb_backup50/BACKUP-2.1.log
share/mysql-test/std_data/ndb_backup50/BACKUP-2.2.ctl
share/mysql-test/std_data/ndb_backup50/BACKUP-2.2.log
share/mysql-test/std_data/ndb_backup51/BACKUP-1-0.1.Data
share/mysql-test/std_data/ndb_backup51/BACKUP-1-0.2.Data
share/mysql-test/std_data/ndb_backup51/BACKUP-1.1.ctl
share/mysql-test/std_data/ndb_backup51/BACKUP-1.1.log
share/mysql-test/std_data/ndb_backup51/BACKUP-1.2.ctl
share/mysql-test/std_data/ndb_backup51/BACKUP-1.2.log
share/mysql-test/std_data/ndb_backup51_data_be/BACKUP-1-0.1.Data
share/mysql-test/std_data/ndb_backup51_data_be/BACKUP-1-0.2.Data
share/mysql-test/std_data/ndb_backup51_data_be/BACKUP-1.1.ctl
share/mysql-test/std_data/ndb_backup51_data_be/BACKUP-1.1.log
share/mysql-test/std_data/ndb_backup51_data_be/BACKUP-1.2.ctl
share/mysql-test/std_data/ndb_backup51_data_be/BACKUP-1.2.log
share/mysql-test/std_data/ndb_backup51_data_le/BACKUP-1-0.1.Data
share/mysql-test/std_data/ndb_backup51_data_le/BACKUP-1-0.2.Data
share/mysql-test/std_data/ndb_backup51_data_le/BACKUP-1.1.ctl
share/mysql-test/std_data/ndb_backup51_data_le/BACKUP-1.1.log
share/mysql-test/std_data/ndb_backup51_data_le/BACKUP-1.2.ctl
share/mysql-test/std_data/ndb_backup51_data_le/BACKUP-1.2.log
share/mysql-test/std_data/ndb_config_config.ini
share/mysql-test/std_data/ndb_config_mycnf1.cnf
share/mysql-test/std_data/ndb_config_mycnf2.cnf
share/mysql-test/std_data/numbers.txt
share/mysql-test/std_data/old_table-323.frm
share/mysql-test/std_data/parts/part_supported_sql_funcs_int_ch1.inc
share/mysql-test/std_data/parts/part_supported_sql_funcs_int_date.inc
share/mysql-test/std_data/parts/part_supported_sql_funcs_int_float.inc
share/mysql-test/std_data/parts/part_supported_sql_funcs_int_int.inc
share/mysql-test/std_data/parts/part_supported_sql_funcs_int_time.inc
share/mysql-test/std_data/parts/t1.frm
Update mysql51-{client,server} package to 5.1.51, MySQL 5.1.51. For full changes, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html Here is summary for security fixes: * Security Fix: During evaluation of arguments to extreme-value functions (such as LEAST() and GREATEST()), type errors did not propagate properly, causing the server to crash. (Bug#55826) * Security Fix: The server could crash after materializing a derived table that required a temporary table for grouping. (Bug#55568) * Security Fix: A user-variable assignment expression that is evaluated in a logical expression context can be precalculated in a temporary table for GROUP BY. However, when the expression value is used after creation of the temporary table, it was re-evaluated, not read from the table and a server crash resulted. (Bug#55564) * Security Fix: Pre-evaluation of LIKE predicates during view preparation could cause a server crash. (Bug#54568) * Security Fix: GROUP_CONCAT() and WITH ROLLUP together could cause a server crash. (Bug#54476) * Security Fix: Queries could cause a server crash if the GREATEST() or LEAST() function had a mixed list of numeric and LONGBLOB arguments, and the result of such a function was processed using an intermediate temporary table. (Bug#54461) * Security Fix: Queries with nested joins could cause an infinite loop in the server when used from stored procedures and prepared statements. (Bug#53544) * Security Fix: The PolyFromWKB() function could crash the server when improper WKB data was passed to the function. (Bug#51875)
2010-10-06 14:37:58 +02:00
share/mysql-test/std_data/parts/t1_blackhole.frm
share/mysql-test/std_data/parts/t1_blackhole.par
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/std_data/parts/t1_will_crash#P#p1_first_1024.MYD
share/mysql-test/std_data/parts/t1_will_crash#P#p2.MYD
share/mysql-test/std_data/parts/t1_will_crash#P#p2.MYI
share/mysql-test/std_data/parts/t1_will_crash#P#p3.MYI
share/mysql-test/std_data/parts/t1_will_crash#P#p4.MYI
share/mysql-test/std_data/parts/t1_will_crash#P#p6.MYD
share/mysql-test/std_data/parts/t1_will_crash#P#p6_2.MYD
share/mysql-test/std_data/parts/t1_will_crash#P#p6_3.MYD
share/mysql-test/std_data/rpl_bug28618.dat
share/mysql-test/std_data/rpl_loaddata.dat
share/mysql-test/std_data/rpl_loaddata2.dat
share/mysql-test/std_data/rpl_mixed.dat
share/mysql-test/std_data/rpl_timezone.dat
share/mysql-test/std_data/rpl_timezone2.dat
share/mysql-test/std_data/server-cert.pem
share/mysql-test/std_data/server-key.pem
share/mysql-test/std_data/server8k-cert.pem
share/mysql-test/std_data/server8k-key.pem
share/mysql-test/std_data/trunc_binlog.000001
share/mysql-test/std_data/untrusted-cacert.pem
share/mysql-test/std_data/vchar.frm
share/mysql-test/std_data/warnings_loaddata.dat
share/mysql-test/std_data/words.dat
share/mysql-test/std_data/words2.dat
share/mysql-test/suite/binlog/combinations
share/mysql-test/suite/binlog/r/binlog_base64_flag.result
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/suite/binlog/r/binlog_bug23533.result
share/mysql-test/suite/binlog/r/binlog_bug36391.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/binlog/r/binlog_database.result
share/mysql-test/suite/binlog/r/binlog_delete_and_flush_index.result
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/binlog/r/binlog_drop_if_exists.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/binlog/r/binlog_grant.result
share/mysql-test/suite/binlog/r/binlog_incident.result
share/mysql-test/suite/binlog/r/binlog_index.result
share/mysql-test/suite/binlog/r/binlog_innodb.result
share/mysql-test/suite/binlog/r/binlog_innodb_row.result
share/mysql-test/suite/binlog/r/binlog_killed.result
share/mysql-test/suite/binlog/r/binlog_killed_simulate.result
share/mysql-test/suite/binlog/r/binlog_mix_innodb_stat.result
share/mysql-test/suite/binlog/r/binlog_mixed_failure_mixing_engines.result
Update mysql51-{client,server} package to 5.1.51, MySQL 5.1.51. For full changes, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html Here is summary for security fixes: * Security Fix: During evaluation of arguments to extreme-value functions (such as LEAST() and GREATEST()), type errors did not propagate properly, causing the server to crash. (Bug#55826) * Security Fix: The server could crash after materializing a derived table that required a temporary table for grouping. (Bug#55568) * Security Fix: A user-variable assignment expression that is evaluated in a logical expression context can be precalculated in a temporary table for GROUP BY. However, when the expression value is used after creation of the temporary table, it was re-evaluated, not read from the table and a server crash resulted. (Bug#55564) * Security Fix: Pre-evaluation of LIKE predicates during view preparation could cause a server crash. (Bug#54568) * Security Fix: GROUP_CONCAT() and WITH ROLLUP together could cause a server crash. (Bug#54476) * Security Fix: Queries could cause a server crash if the GREATEST() or LEAST() function had a mixed list of numeric and LONGBLOB arguments, and the result of such a function was processed using an intermediate temporary table. (Bug#54461) * Security Fix: Queries with nested joins could cause an infinite loop in the server when used from stored procedures and prepared statements. (Bug#53544) * Security Fix: The PolyFromWKB() function could crash the server when improper WKB data was passed to the function. (Bug#51875)
2010-10-06 14:37:58 +02:00
share/mysql-test/suite/binlog/r/binlog_mixed_load_data.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/binlog/r/binlog_multi_engine.result
Changes 5.1.67: Bug fixes http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-67.html
2013-01-21 09:58:43 +01:00
share/mysql-test/suite/binlog/r/binlog_mysqlbinlog-cp932.result
share/mysql-test/suite/binlog/r/binlog_mysqlbinlog2.result
share/mysql-test/suite/binlog/r/binlog_mysqlbinlog_base64.result
share/mysql-test/suite/binlog/r/binlog_mysqlbinlog_row.result
share/mysql-test/suite/binlog/r/binlog_mysqlbinlog_row_innodb.result
share/mysql-test/suite/binlog/r/binlog_mysqlbinlog_row_myisam.result
share/mysql-test/suite/binlog/r/binlog_mysqlbinlog_row_trans.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/binlog/r/binlog_old_versions.result
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/binlog/r/binlog_query_filter_rules.result
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/suite/binlog/r/binlog_reset_master.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/binlog/r/binlog_row_binlog.result
share/mysql-test/suite/binlog/r/binlog_row_ctype_cp932.result
share/mysql-test/suite/binlog/r/binlog_row_ctype_ucs.result
share/mysql-test/suite/binlog/r/binlog_row_drop_tmp_tbl.result
share/mysql-test/suite/binlog/r/binlog_row_failure_mixing_engines.result
share/mysql-test/suite/binlog/r/binlog_row_innodb_stat.result
share/mysql-test/suite/binlog/r/binlog_row_insert_select.result
share/mysql-test/suite/binlog/r/binlog_row_mix_innodb_myisam.result
share/mysql-test/suite/binlog/r/binlog_row_mysqlbinlog_db_filter.result
share/mysql-test/suite/binlog/r/binlog_row_mysqlbinlog_verbose.result
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/binlog/r/binlog_server_id.result
share/mysql-test/suite/binlog/r/binlog_sf.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/binlog/r/binlog_sql_mode.result
share/mysql-test/suite/binlog/r/binlog_start_comment.result
share/mysql-test/suite/binlog/r/binlog_statement_insert_delayed.result
share/mysql-test/suite/binlog/r/binlog_stm_binlog.result
share/mysql-test/suite/binlog/r/binlog_stm_blackhole.result
share/mysql-test/suite/binlog/r/binlog_stm_ctype_cp932.result
share/mysql-test/suite/binlog/r/binlog_stm_ctype_ucs.result
share/mysql-test/suite/binlog/r/binlog_stm_do_db.result
share/mysql-test/suite/binlog/r/binlog_stm_drop_tmp_tbl.result
share/mysql-test/suite/binlog/r/binlog_stm_innodb_stat.result
share/mysql-test/suite/binlog/r/binlog_stm_insert_select.result
share/mysql-test/suite/binlog/r/binlog_stm_mix_innodb_myisam.result
share/mysql-test/suite/binlog/r/binlog_stm_ps.result
share/mysql-test/suite/binlog/r/binlog_stm_row.result
share/mysql-test/suite/binlog/r/binlog_stm_unsafe_warning.result
share/mysql-test/suite/binlog/r/binlog_tmp_table.result
share/mysql-test/suite/binlog/r/binlog_truncate_innodb.result
share/mysql-test/suite/binlog/r/binlog_truncate_myisam.result
share/mysql-test/suite/binlog/r/binlog_unsafe.result
share/mysql-test/suite/binlog/r/binlog_write_error.result
share/mysql-test/suite/binlog/std_data/binlog_old_version_4_1.000001
share/mysql-test/suite/binlog/std_data/bug32407.001
share/mysql-test/suite/binlog/std_data/update-full-row.binlog
share/mysql-test/suite/binlog/std_data/update-partial-row.binlog
share/mysql-test/suite/binlog/std_data/ver_5_1-telco.001
share/mysql-test/suite/binlog/std_data/ver_5_1-wl2325_r.001
share/mysql-test/suite/binlog/std_data/ver_5_1-wl2325_s.001
share/mysql-test/suite/binlog/std_data/ver_5_1_17.001
share/mysql-test/suite/binlog/std_data/ver_5_1_23.001
share/mysql-test/suite/binlog/std_data/write-full-row.binlog
share/mysql-test/suite/binlog/std_data/write-partial-row.binlog
share/mysql-test/suite/binlog/t/binlog_base64_flag.test
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/suite/binlog/t/binlog_bug23533.test
share/mysql-test/suite/binlog/t/binlog_bug36391-master.opt
share/mysql-test/suite/binlog/t/binlog_bug36391.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/binlog/t/binlog_database.test
share/mysql-test/suite/binlog/t/binlog_delete_and_flush_index.test
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/binlog/t/binlog_drop_if_exists.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/binlog/t/binlog_grant.test
share/mysql-test/suite/binlog/t/binlog_incident-master.opt
share/mysql-test/suite/binlog/t/binlog_incident.test
Update mysql51-{client,server} package to 5.1.54. Functionality added or changed: * Support for the IBMDB2I storage engine has been removed. (Bug#58079) * The pstack library was nonfunctional and has been removed, along with the --with-pstack option for configure. The --enable-pstack option for mysqld is deprecated and will be removed in MySQL 5.5. (Bug#57210) Bugs fixed: * Performance: InnoDB Storage Engine: Improved concurrency when several ANALYZE TABLE or SHOW TABLE STATUS statements are run simultaneously for InnoDB tables. (Bug#53046) * InnoDB Storage Engine: For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#57799) * Partitioning: An INSERT ... ON DUPLICATE KEY UPDATE column = 0 statement on an AUTO_INCREMENT column caused the debug server to crash. (Bug#57890) * Several compilation problems were fixed. (Bug#57992, Bug#57993, Bug#57994, Bug#57995, Bug#57996, Bug#57997, Bug#58057) * Passing a string that was not null-terminated to UpdateXML() or ExtractValue() caused the server to fail with an assertion. (Bug#57279) * Queries executed using the Index Merge access method and a temporary file could return incorrect results. (Bug#56862) * The find_files() function used by SHOW statements performed redundant and unnecessary memory allocation. (Bug#51208)
2010-12-16 04:42:49 +01:00
share/mysql-test/suite/binlog/t/binlog_index-master.opt
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/binlog/t/binlog_index.test
share/mysql-test/suite/binlog/t/binlog_innodb.test
share/mysql-test/suite/binlog/t/binlog_innodb_row.test
share/mysql-test/suite/binlog/t/binlog_killed.test
share/mysql-test/suite/binlog/t/binlog_killed_simulate-master.opt
share/mysql-test/suite/binlog/t/binlog_killed_simulate.test
share/mysql-test/suite/binlog/t/binlog_mix_innodb_stat.test
share/mysql-test/suite/binlog/t/binlog_mixed_failure_mixing_engines.test
Update mysql51-{client,server} package to 5.1.51, MySQL 5.1.51. For full changes, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html Here is summary for security fixes: * Security Fix: During evaluation of arguments to extreme-value functions (such as LEAST() and GREATEST()), type errors did not propagate properly, causing the server to crash. (Bug#55826) * Security Fix: The server could crash after materializing a derived table that required a temporary table for grouping. (Bug#55568) * Security Fix: A user-variable assignment expression that is evaluated in a logical expression context can be precalculated in a temporary table for GROUP BY. However, when the expression value is used after creation of the temporary table, it was re-evaluated, not read from the table and a server crash resulted. (Bug#55564) * Security Fix: Pre-evaluation of LIKE predicates during view preparation could cause a server crash. (Bug#54568) * Security Fix: GROUP_CONCAT() and WITH ROLLUP together could cause a server crash. (Bug#54476) * Security Fix: Queries could cause a server crash if the GREATEST() or LEAST() function had a mixed list of numeric and LONGBLOB arguments, and the result of such a function was processed using an intermediate temporary table. (Bug#54461) * Security Fix: Queries with nested joins could cause an infinite loop in the server when used from stored procedures and prepared statements. (Bug#53544) * Security Fix: The PolyFromWKB() function could crash the server when improper WKB data was passed to the function. (Bug#51875)
2010-10-06 14:37:58 +02:00
share/mysql-test/suite/binlog/t/binlog_mixed_load_data.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/binlog/t/binlog_multi_engine.test
Changes 5.1.67: Bug fixes http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-67.html
2013-01-21 09:58:43 +01:00
share/mysql-test/suite/binlog/t/binlog_mysqlbinlog-cp932-master.opt
share/mysql-test/suite/binlog/t/binlog_mysqlbinlog-cp932.test
share/mysql-test/suite/binlog/t/binlog_mysqlbinlog2.test
share/mysql-test/suite/binlog/t/binlog_mysqlbinlog_base64.test
share/mysql-test/suite/binlog/t/binlog_mysqlbinlog_row.test
share/mysql-test/suite/binlog/t/binlog_mysqlbinlog_row_innodb.test
share/mysql-test/suite/binlog/t/binlog_mysqlbinlog_row_myisam.test
share/mysql-test/suite/binlog/t/binlog_mysqlbinlog_row_trans.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/binlog/t/binlog_old_versions.test
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/binlog/t/binlog_query_filter_rules-master.opt
share/mysql-test/suite/binlog/t/binlog_query_filter_rules.test
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/suite/binlog/t/binlog_reset_master.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/binlog/t/binlog_row_binlog-master.opt
share/mysql-test/suite/binlog/t/binlog_row_binlog.test
share/mysql-test/suite/binlog/t/binlog_row_ctype_cp932.test
share/mysql-test/suite/binlog/t/binlog_row_ctype_ucs.test
share/mysql-test/suite/binlog/t/binlog_row_drop_tmp_tbl.test
share/mysql-test/suite/binlog/t/binlog_row_failure_mixing_engines.test
share/mysql-test/suite/binlog/t/binlog_row_innodb_stat-master.opt
share/mysql-test/suite/binlog/t/binlog_row_innodb_stat.test
share/mysql-test/suite/binlog/t/binlog_row_insert_select.test
share/mysql-test/suite/binlog/t/binlog_row_mix_innodb_myisam-master.opt
share/mysql-test/suite/binlog/t/binlog_row_mix_innodb_myisam.test
share/mysql-test/suite/binlog/t/binlog_row_mysqlbinlog_db_filter.test
share/mysql-test/suite/binlog/t/binlog_row_mysqlbinlog_verbose.test
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/binlog/t/binlog_server_id.test
share/mysql-test/suite/binlog/t/binlog_sf.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/binlog/t/binlog_sql_mode.test
share/mysql-test/suite/binlog/t/binlog_start_comment.test
share/mysql-test/suite/binlog/t/binlog_statement_insert_delayed.test
share/mysql-test/suite/binlog/t/binlog_stm_binlog-master.opt
share/mysql-test/suite/binlog/t/binlog_stm_binlog.test
share/mysql-test/suite/binlog/t/binlog_stm_blackhole.test
share/mysql-test/suite/binlog/t/binlog_stm_ctype_cp932.test
share/mysql-test/suite/binlog/t/binlog_stm_ctype_ucs.test
share/mysql-test/suite/binlog/t/binlog_stm_do_db-master.opt
share/mysql-test/suite/binlog/t/binlog_stm_do_db.test
share/mysql-test/suite/binlog/t/binlog_stm_drop_tmp_tbl.test
share/mysql-test/suite/binlog/t/binlog_stm_innodb_stat-master.opt
share/mysql-test/suite/binlog/t/binlog_stm_innodb_stat.test
share/mysql-test/suite/binlog/t/binlog_stm_insert_select.test
share/mysql-test/suite/binlog/t/binlog_stm_mix_innodb_myisam-master.opt
share/mysql-test/suite/binlog/t/binlog_stm_mix_innodb_myisam.test
share/mysql-test/suite/binlog/t/binlog_stm_ps.test
share/mysql-test/suite/binlog/t/binlog_stm_row.test
share/mysql-test/suite/binlog/t/binlog_stm_unsafe_warning-master.opt
share/mysql-test/suite/binlog/t/binlog_stm_unsafe_warning.test
share/mysql-test/suite/binlog/t/binlog_tmp_table.test
share/mysql-test/suite/binlog/t/binlog_truncate_innodb-master.opt
share/mysql-test/suite/binlog/t/binlog_truncate_innodb.test
share/mysql-test/suite/binlog/t/binlog_truncate_myisam.test
share/mysql-test/suite/binlog/t/binlog_unsafe.test
share/mysql-test/suite/binlog/t/binlog_write_error.test
share/mysql-test/suite/binlog/t/disabled.def
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/suite/engines/README
share/mysql-test/suite/engines/funcs/r/ai_init_alter_table.result
share/mysql-test/suite/engines/funcs/r/ai_init_create_table.result
share/mysql-test/suite/engines/funcs/r/ai_init_insert.result
share/mysql-test/suite/engines/funcs/r/ai_init_insert_id.result
share/mysql-test/suite/engines/funcs/r/ai_overflow_error.result
share/mysql-test/suite/engines/funcs/r/ai_reset_by_truncate.result
share/mysql-test/suite/engines/funcs/r/ai_sql_auto_is_null.result
share/mysql-test/suite/engines/funcs/r/an_calendar.result
share/mysql-test/suite/engines/funcs/r/an_number.result
share/mysql-test/suite/engines/funcs/r/an_string.result
share/mysql-test/suite/engines/funcs/r/comment_column.result
share/mysql-test/suite/engines/funcs/r/comment_column2.result
share/mysql-test/suite/engines/funcs/r/comment_table.result
share/mysql-test/suite/engines/funcs/r/crash_manycolumns_number.result
share/mysql-test/suite/engines/funcs/r/crash_manycolumns_string.result
share/mysql-test/suite/engines/funcs/r/crash_manyindexes_number.result
share/mysql-test/suite/engines/funcs/r/crash_manyindexes_string.result
share/mysql-test/suite/engines/funcs/r/crash_manytables_number.result
share/mysql-test/suite/engines/funcs/r/crash_manytables_string.result
share/mysql-test/suite/engines/funcs/r/date_function.result
share/mysql-test/suite/engines/funcs/r/datetime_function.result
share/mysql-test/suite/engines/funcs/r/db_alter_character_set.result
share/mysql-test/suite/engines/funcs/r/db_alter_character_set_collate.result
share/mysql-test/suite/engines/funcs/r/db_alter_collate_ascii.result
share/mysql-test/suite/engines/funcs/r/db_alter_collate_utf8.result
share/mysql-test/suite/engines/funcs/r/db_create_character_set.result
share/mysql-test/suite/engines/funcs/r/db_create_character_set_collate.result
share/mysql-test/suite/engines/funcs/r/db_create_drop.result
share/mysql-test/suite/engines/funcs/r/db_create_error.result
share/mysql-test/suite/engines/funcs/r/db_create_error_reserved.result
share/mysql-test/suite/engines/funcs/r/db_create_if_not_exists.result
share/mysql-test/suite/engines/funcs/r/db_drop_error.result
share/mysql-test/suite/engines/funcs/r/db_use_error.result
share/mysql-test/suite/engines/funcs/r/de_autoinc.result
share/mysql-test/suite/engines/funcs/r/de_calendar_range.result
share/mysql-test/suite/engines/funcs/r/de_ignore.result
share/mysql-test/suite/engines/funcs/r/de_limit.result
share/mysql-test/suite/engines/funcs/r/de_multi_db_table.result
share/mysql-test/suite/engines/funcs/r/de_multi_db_table_using.result
share/mysql-test/suite/engines/funcs/r/de_multi_table.result
share/mysql-test/suite/engines/funcs/r/de_multi_table_using.result
share/mysql-test/suite/engines/funcs/r/de_number_range.result
share/mysql-test/suite/engines/funcs/r/de_quick.result
share/mysql-test/suite/engines/funcs/r/de_string_range.result
share/mysql-test/suite/engines/funcs/r/de_truncate.result
share/mysql-test/suite/engines/funcs/r/de_truncate_autoinc.result
share/mysql-test/suite/engines/funcs/r/fu_aggregate_avg_number.result
share/mysql-test/suite/engines/funcs/r/fu_aggregate_count_number.result
share/mysql-test/suite/engines/funcs/r/fu_aggregate_max_number.result
share/mysql-test/suite/engines/funcs/r/fu_aggregate_max_subquery.result
share/mysql-test/suite/engines/funcs/r/fu_aggregate_min_number.result
share/mysql-test/suite/engines/funcs/r/fu_aggregate_sum_number.result
share/mysql-test/suite/engines/funcs/r/general_no_data.result
share/mysql-test/suite/engines/funcs/r/general_not_null.result
share/mysql-test/suite/engines/funcs/r/general_null.result
share/mysql-test/suite/engines/funcs/r/in_calendar_2_unique_constraints_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_calendar_pk_constraint_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_calendar_pk_constraint_error.result
share/mysql-test/suite/engines/funcs/r/in_calendar_pk_constraint_ignore.result
share/mysql-test/suite/engines/funcs/r/in_calendar_unique_constraint_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_calendar_unique_constraint_error.result
share/mysql-test/suite/engines/funcs/r/in_calendar_unique_constraint_ignore.result
share/mysql-test/suite/engines/funcs/r/in_enum_null.result
share/mysql-test/suite/engines/funcs/r/in_enum_null_boundary_error.result
share/mysql-test/suite/engines/funcs/r/in_enum_null_large_error.result
share/mysql-test/suite/engines/funcs/r/in_insert_select.result
share/mysql-test/suite/engines/funcs/r/in_insert_select_autoinc.result
share/mysql-test/suite/engines/funcs/r/in_insert_select_unique_violation.result
share/mysql-test/suite/engines/funcs/r/in_lob_boundary_error.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_calendar_pk_constraint_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_calendar_pk_constraint_error.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_calendar_pk_constraint_ignore.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_calendar_unique_constraint_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_calendar_unique_constraint_error.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_calendar_unique_constraint_ignore.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_number_pk_constraint_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_number_pk_constraint_error.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_number_pk_constraint_ignore.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_number_unique_constraint_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_number_unique_constraint_error.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_number_unique_constraint_ignore.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_string_pk_constraint_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_string_pk_constraint_error.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_string_pk_constraint_ignore.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_string_unique_constraint_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_string_unique_constraint_error.result
share/mysql-test/suite/engines/funcs/r/in_multicolumn_string_unique_constraint_ignore.result
share/mysql-test/suite/engines/funcs/r/in_number_2_unique_constraints_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_number_boundary_error.result
share/mysql-test/suite/engines/funcs/r/in_number_decimal_boundary_error.result
share/mysql-test/suite/engines/funcs/r/in_number_length.result
share/mysql-test/suite/engines/funcs/r/in_number_null.result
share/mysql-test/suite/engines/funcs/r/in_number_pk_constraint_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_number_pk_constraint_error.result
share/mysql-test/suite/engines/funcs/r/in_number_pk_constraint_ignore.result
share/mysql-test/suite/engines/funcs/r/in_number_unique_constraint_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_number_unique_constraint_error.result
share/mysql-test/suite/engines/funcs/r/in_number_unique_constraint_ignore.result
share/mysql-test/suite/engines/funcs/r/in_set_null.result
share/mysql-test/suite/engines/funcs/r/in_set_null_boundary_error.result
share/mysql-test/suite/engines/funcs/r/in_set_null_large.result
share/mysql-test/suite/engines/funcs/r/in_string_2_unique_constraints_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_string_boundary_error.result
share/mysql-test/suite/engines/funcs/r/in_string_not_null.result
share/mysql-test/suite/engines/funcs/r/in_string_null.result
share/mysql-test/suite/engines/funcs/r/in_string_pk_constraint_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_string_pk_constraint_error.result
share/mysql-test/suite/engines/funcs/r/in_string_pk_constraint_ignore.result
share/mysql-test/suite/engines/funcs/r/in_string_set_enum_fail.result
share/mysql-test/suite/engines/funcs/r/in_string_unique_constraint_duplicate_update.result
share/mysql-test/suite/engines/funcs/r/in_string_unique_constraint_error.result
share/mysql-test/suite/engines/funcs/r/in_string_unique_constraint_ignore.result
share/mysql-test/suite/engines/funcs/r/ix_drop.result
share/mysql-test/suite/engines/funcs/r/ix_drop_error.result
share/mysql-test/suite/engines/funcs/r/ix_index_decimals.result
share/mysql-test/suite/engines/funcs/r/ix_index_lob.result
share/mysql-test/suite/engines/funcs/r/ix_index_non_string.result
share/mysql-test/suite/engines/funcs/r/ix_index_string.result
share/mysql-test/suite/engines/funcs/r/ix_index_string_length.result
share/mysql-test/suite/engines/funcs/r/ix_unique_decimals.result
share/mysql-test/suite/engines/funcs/r/ix_unique_lob.result
share/mysql-test/suite/engines/funcs/r/ix_unique_non_string.result
share/mysql-test/suite/engines/funcs/r/ix_unique_string.result
share/mysql-test/suite/engines/funcs/r/ix_unique_string_length.result
share/mysql-test/suite/engines/funcs/r/ix_using_order.result
share/mysql-test/suite/engines/funcs/r/jp_comment_column.result
share/mysql-test/suite/engines/funcs/r/jp_comment_older_compatibility1.result
share/mysql-test/suite/engines/funcs/r/jp_comment_table.result
share/mysql-test/suite/engines/funcs/r/ld_all_number_string_calendar_types.result
share/mysql-test/suite/engines/funcs/r/ld_bit.result
share/mysql-test/suite/engines/funcs/r/ld_enum_set.result
share/mysql-test/suite/engines/funcs/r/ld_less_columns.result
share/mysql-test/suite/engines/funcs/r/ld_more_columns_truncated.result
share/mysql-test/suite/engines/funcs/r/ld_null.result
share/mysql-test/suite/engines/funcs/r/ld_quote.result
share/mysql-test/suite/engines/funcs/r/ld_simple.result
share/mysql-test/suite/engines/funcs/r/ld_starting.result
share/mysql-test/suite/engines/funcs/r/ld_unique_error1.result
share/mysql-test/suite/engines/funcs/r/ld_unique_error1_local.result
share/mysql-test/suite/engines/funcs/r/ld_unique_error2.result
share/mysql-test/suite/engines/funcs/r/ld_unique_error2_local.result
share/mysql-test/suite/engines/funcs/r/ld_unique_error3.result
share/mysql-test/suite/engines/funcs/r/ld_unique_error3_local.result
share/mysql-test/suite/engines/funcs/r/ps_number_length.result
share/mysql-test/suite/engines/funcs/r/ps_number_null.result
share/mysql-test/suite/engines/funcs/r/ps_string_not_null.result
share/mysql-test/suite/engines/funcs/r/ps_string_null.result
share/mysql-test/suite/engines/funcs/r/re_number_range.result
share/mysql-test/suite/engines/funcs/r/re_number_range_set.result
share/mysql-test/suite/engines/funcs/r/re_number_select.result
share/mysql-test/suite/engines/funcs/r/re_string_range.result
share/mysql-test/suite/engines/funcs/r/re_string_range_set.result
share/mysql-test/suite/engines/funcs/r/rpl000010.result
share/mysql-test/suite/engines/funcs/r/rpl000011.result
share/mysql-test/suite/engines/funcs/r/rpl000013.result
share/mysql-test/suite/engines/funcs/r/rpl000017.result
share/mysql-test/suite/engines/funcs/r/rpl_000015.result
share/mysql-test/suite/engines/funcs/r/rpl_LD_INFILE.result
share/mysql-test/suite/engines/funcs/r/rpl_REDIRECT.result
share/mysql-test/suite/engines/funcs/r/rpl_alter.result
share/mysql-test/suite/engines/funcs/r/rpl_alter_db.result
share/mysql-test/suite/engines/funcs/r/rpl_bit.result
share/mysql-test/suite/engines/funcs/r/rpl_bit_npk.result
share/mysql-test/suite/engines/funcs/r/rpl_change_master.result
share/mysql-test/suite/engines/funcs/r/rpl_create_database.result
share/mysql-test/suite/engines/funcs/r/rpl_do_grant.result
share/mysql-test/suite/engines/funcs/r/rpl_drop.result
share/mysql-test/suite/engines/funcs/r/rpl_drop_db.result
share/mysql-test/suite/engines/funcs/r/rpl_dual_pos_advance.result
share/mysql-test/suite/engines/funcs/r/rpl_empty_master_crash.result
share/mysql-test/suite/engines/funcs/r/rpl_err_ignoredtable.result
share/mysql-test/suite/engines/funcs/r/rpl_flushlog_loop.result
share/mysql-test/suite/engines/funcs/r/rpl_free_items.result
share/mysql-test/suite/engines/funcs/r/rpl_get_lock.result
share/mysql-test/suite/engines/funcs/r/rpl_ignore_grant.result
share/mysql-test/suite/engines/funcs/r/rpl_ignore_revoke.result
share/mysql-test/suite/engines/funcs/r/rpl_ignore_table_update.result
share/mysql-test/suite/engines/funcs/r/rpl_init_slave.result
share/mysql-test/suite/engines/funcs/r/rpl_insert.result
share/mysql-test/suite/engines/funcs/r/rpl_insert_select.result
share/mysql-test/suite/engines/funcs/r/rpl_loaddata2.result
share/mysql-test/suite/engines/funcs/r/rpl_loaddata_m.result
share/mysql-test/suite/engines/funcs/r/rpl_loaddata_s.result
share/mysql-test/suite/engines/funcs/r/rpl_loaddatalocal.result
share/mysql-test/suite/engines/funcs/r/rpl_loadfile.result
share/mysql-test/suite/engines/funcs/r/rpl_log_pos.result
share/mysql-test/suite/engines/funcs/r/rpl_many_optimize.result
share/mysql-test/suite/engines/funcs/r/rpl_master_pos_wait.result
share/mysql-test/suite/engines/funcs/r/rpl_misc_functions.result
share/mysql-test/suite/engines/funcs/r/rpl_multi_delete.result
share/mysql-test/suite/engines/funcs/r/rpl_multi_delete2.result
share/mysql-test/suite/engines/funcs/r/rpl_multi_update4.result
share/mysql-test/suite/engines/funcs/r/rpl_ps.result
share/mysql-test/suite/engines/funcs/r/rpl_rbr_to_sbr.result
share/mysql-test/suite/engines/funcs/r/rpl_relayspace.result
share/mysql-test/suite/engines/funcs/r/rpl_replicate_ignore_db.result
share/mysql-test/suite/engines/funcs/r/rpl_row_NOW.result
share/mysql-test/suite/engines/funcs/r/rpl_row_USER.result
share/mysql-test/suite/engines/funcs/r/rpl_row_drop.result
share/mysql-test/suite/engines/funcs/r/rpl_row_func001.result
share/mysql-test/suite/engines/funcs/r/rpl_row_inexist_tbl.result
share/mysql-test/suite/engines/funcs/r/rpl_row_max_relay_size.result
share/mysql-test/suite/engines/funcs/r/rpl_row_reset_slave.result
share/mysql-test/suite/engines/funcs/r/rpl_row_sp001.result
share/mysql-test/suite/engines/funcs/r/rpl_row_sp005.result
share/mysql-test/suite/engines/funcs/r/rpl_row_sp008.result
share/mysql-test/suite/engines/funcs/r/rpl_row_sp009.result
share/mysql-test/suite/engines/funcs/r/rpl_row_sp010.result
share/mysql-test/suite/engines/funcs/r/rpl_row_sp011.result
share/mysql-test/suite/engines/funcs/r/rpl_row_sp012.result
share/mysql-test/suite/engines/funcs/r/rpl_row_stop_middle.result
share/mysql-test/suite/engines/funcs/r/rpl_row_trig001.result
share/mysql-test/suite/engines/funcs/r/rpl_row_trig002.result
share/mysql-test/suite/engines/funcs/r/rpl_row_trig003.result
share/mysql-test/suite/engines/funcs/r/rpl_row_until.result
share/mysql-test/suite/engines/funcs/r/rpl_row_view01.result
share/mysql-test/suite/engines/funcs/r/rpl_server_id1.result
share/mysql-test/suite/engines/funcs/r/rpl_server_id2.result
share/mysql-test/suite/engines/funcs/r/rpl_session_var.result
share/mysql-test/suite/engines/funcs/r/rpl_sf.result
share/mysql-test/suite/engines/funcs/r/rpl_skip_error.result
share/mysql-test/suite/engines/funcs/r/rpl_slave_status.result
share/mysql-test/suite/engines/funcs/r/rpl_sp.result
share/mysql-test/suite/engines/funcs/r/rpl_sp004.result
share/mysql-test/suite/engines/funcs/r/rpl_sp_effects.result
share/mysql-test/suite/engines/funcs/r/rpl_start_stop_slave.result
share/mysql-test/suite/engines/funcs/r/rpl_stm_max_relay_size.result
share/mysql-test/suite/engines/funcs/r/rpl_stm_mystery22.result
share/mysql-test/suite/engines/funcs/r/rpl_stm_no_op.result
share/mysql-test/suite/engines/funcs/r/rpl_stm_reset_slave.result
share/mysql-test/suite/engines/funcs/r/rpl_switch_stm_row_mixed.result
share/mysql-test/suite/engines/funcs/r/rpl_temp_table.result
share/mysql-test/suite/engines/funcs/r/rpl_temporary.result
share/mysql-test/suite/engines/funcs/r/rpl_trigger.result
share/mysql-test/suite/engines/funcs/r/rpl_trunc_temp.result
share/mysql-test/suite/engines/funcs/r/rpl_user_variables.result
share/mysql-test/suite/engines/funcs/r/rpl_variables.result
share/mysql-test/suite/engines/funcs/r/rpl_view.result
share/mysql-test/suite/engines/funcs/r/se_join_cross.result
share/mysql-test/suite/engines/funcs/r/se_join_default.result
share/mysql-test/suite/engines/funcs/r/se_join_inner.result
share/mysql-test/suite/engines/funcs/r/se_join_left.result
share/mysql-test/suite/engines/funcs/r/se_join_left_outer.result
share/mysql-test/suite/engines/funcs/r/se_join_natural_left.result
share/mysql-test/suite/engines/funcs/r/se_join_natural_left_outer.result
share/mysql-test/suite/engines/funcs/r/se_join_natural_right.result
share/mysql-test/suite/engines/funcs/r/se_join_natural_right_outer.result
share/mysql-test/suite/engines/funcs/r/se_join_right.result
share/mysql-test/suite/engines/funcs/r/se_join_right_outer.result
share/mysql-test/suite/engines/funcs/r/se_join_straight.result
share/mysql-test/suite/engines/funcs/r/se_rowid.result
share/mysql-test/suite/engines/funcs/r/se_string_distinct.result
share/mysql-test/suite/engines/funcs/r/se_string_from.result
share/mysql-test/suite/engines/funcs/r/se_string_groupby.result
share/mysql-test/suite/engines/funcs/r/se_string_having.result
share/mysql-test/suite/engines/funcs/r/se_string_limit.result
share/mysql-test/suite/engines/funcs/r/se_string_orderby.result
share/mysql-test/suite/engines/funcs/r/se_string_union.result
share/mysql-test/suite/engines/funcs/r/se_string_where.result
share/mysql-test/suite/engines/funcs/r/se_string_where_and.result
share/mysql-test/suite/engines/funcs/r/se_string_where_or.result
share/mysql-test/suite/engines/funcs/r/sf_alter.result
share/mysql-test/suite/engines/funcs/r/sf_cursor.result
share/mysql-test/suite/engines/funcs/r/sf_simple1.result
share/mysql-test/suite/engines/funcs/r/sp_alter.result
share/mysql-test/suite/engines/funcs/r/sp_cursor.result
share/mysql-test/suite/engines/funcs/r/sp_simple1.result
share/mysql-test/suite/engines/funcs/r/sq_all.result
share/mysql-test/suite/engines/funcs/r/sq_any.result
share/mysql-test/suite/engines/funcs/r/sq_corr.result
share/mysql-test/suite/engines/funcs/r/sq_error.result
share/mysql-test/suite/engines/funcs/r/sq_exists.result
share/mysql-test/suite/engines/funcs/r/sq_from.result
share/mysql-test/suite/engines/funcs/r/sq_in.result
share/mysql-test/suite/engines/funcs/r/sq_row.result
share/mysql-test/suite/engines/funcs/r/sq_scalar.result
share/mysql-test/suite/engines/funcs/r/sq_some.result
share/mysql-test/suite/engines/funcs/r/ta_2part_column_to_pk.result
share/mysql-test/suite/engines/funcs/r/ta_2part_diff_string_to_pk.result
share/mysql-test/suite/engines/funcs/r/ta_2part_diff_to_pk.result
share/mysql-test/suite/engines/funcs/r/ta_2part_string_to_pk.result
share/mysql-test/suite/engines/funcs/r/ta_3part_column_to_pk.result
share/mysql-test/suite/engines/funcs/r/ta_3part_string_to_pk.result
share/mysql-test/suite/engines/funcs/r/ta_add_column.result
share/mysql-test/suite/engines/funcs/r/ta_add_column2.result
share/mysql-test/suite/engines/funcs/r/ta_add_column_first.result
share/mysql-test/suite/engines/funcs/r/ta_add_column_first2.result
share/mysql-test/suite/engines/funcs/r/ta_add_column_middle.result
share/mysql-test/suite/engines/funcs/r/ta_add_column_middle2.result
share/mysql-test/suite/engines/funcs/r/ta_add_string.result
share/mysql-test/suite/engines/funcs/r/ta_add_string2.result
share/mysql-test/suite/engines/funcs/r/ta_add_string_first.result
share/mysql-test/suite/engines/funcs/r/ta_add_string_first2.result
share/mysql-test/suite/engines/funcs/r/ta_add_string_middle.result
share/mysql-test/suite/engines/funcs/r/ta_add_string_middle2.result
share/mysql-test/suite/engines/funcs/r/ta_add_string_unique_index.result
share/mysql-test/suite/engines/funcs/r/ta_add_unique_index.result
share/mysql-test/suite/engines/funcs/r/ta_column_from_unsigned.result
share/mysql-test/suite/engines/funcs/r/ta_column_from_zerofill.result
share/mysql-test/suite/engines/funcs/r/ta_column_to_index.result
share/mysql-test/suite/engines/funcs/r/ta_column_to_not_null.result
share/mysql-test/suite/engines/funcs/r/ta_column_to_null.result
share/mysql-test/suite/engines/funcs/r/ta_column_to_pk.result
share/mysql-test/suite/engines/funcs/r/ta_column_to_unsigned.result
share/mysql-test/suite/engines/funcs/r/ta_column_to_zerofill.result
share/mysql-test/suite/engines/funcs/r/ta_drop_column.result
share/mysql-test/suite/engines/funcs/r/ta_drop_index.result
share/mysql-test/suite/engines/funcs/r/ta_drop_pk_autoincrement.result
share/mysql-test/suite/engines/funcs/r/ta_drop_pk_number.result
share/mysql-test/suite/engines/funcs/r/ta_drop_pk_string.result
share/mysql-test/suite/engines/funcs/r/ta_drop_string_index.result
share/mysql-test/suite/engines/funcs/r/ta_orderby.result
share/mysql-test/suite/engines/funcs/r/ta_rename.result
share/mysql-test/suite/engines/funcs/r/ta_set_drop_default.result
share/mysql-test/suite/engines/funcs/r/ta_string_drop_column.result
share/mysql-test/suite/engines/funcs/r/ta_string_to_index.result
share/mysql-test/suite/engines/funcs/r/ta_string_to_not_null.result
share/mysql-test/suite/engines/funcs/r/ta_string_to_null.result
share/mysql-test/suite/engines/funcs/r/ta_string_to_pk.result
share/mysql-test/suite/engines/funcs/r/tc_column_autoincrement.result
share/mysql-test/suite/engines/funcs/r/tc_column_comment.result
share/mysql-test/suite/engines/funcs/r/tc_column_comment_string.result
share/mysql-test/suite/engines/funcs/r/tc_column_default_decimal.result
share/mysql-test/suite/engines/funcs/r/tc_column_default_number.result
share/mysql-test/suite/engines/funcs/r/tc_column_default_string.result
share/mysql-test/suite/engines/funcs/r/tc_column_enum.result
share/mysql-test/suite/engines/funcs/r/tc_column_enum_long.result
share/mysql-test/suite/engines/funcs/r/tc_column_key.result
share/mysql-test/suite/engines/funcs/r/tc_column_key_length.result
share/mysql-test/suite/engines/funcs/r/tc_column_length.result
share/mysql-test/suite/engines/funcs/r/tc_column_length_decimals.result
share/mysql-test/suite/engines/funcs/r/tc_column_length_zero.result
share/mysql-test/suite/engines/funcs/r/tc_column_not_null.result
share/mysql-test/suite/engines/funcs/r/tc_column_null.result
share/mysql-test/suite/engines/funcs/r/tc_column_primary_key_number.result
share/mysql-test/suite/engines/funcs/r/tc_column_primary_key_string.result
share/mysql-test/suite/engines/funcs/r/tc_column_serial.result
share/mysql-test/suite/engines/funcs/r/tc_column_set.result
share/mysql-test/suite/engines/funcs/r/tc_column_set_long.result
share/mysql-test/suite/engines/funcs/r/tc_column_unique_key.result
share/mysql-test/suite/engines/funcs/r/tc_column_unique_key_string.result
share/mysql-test/suite/engines/funcs/r/tc_column_unsigned.result
share/mysql-test/suite/engines/funcs/r/tc_column_zerofill.result
share/mysql-test/suite/engines/funcs/r/tc_drop_table.result
share/mysql-test/suite/engines/funcs/r/tc_multicolumn_different.result
share/mysql-test/suite/engines/funcs/r/tc_multicolumn_same.result
share/mysql-test/suite/engines/funcs/r/tc_multicolumn_same_string.result
share/mysql-test/suite/engines/funcs/r/tc_partition_analyze.result
share/mysql-test/suite/engines/funcs/r/tc_partition_change_from_range_to_hash_key.result
share/mysql-test/suite/engines/funcs/r/tc_partition_check.result
share/mysql-test/suite/engines/funcs/r/tc_partition_hash.result
share/mysql-test/suite/engines/funcs/r/tc_partition_hash_date_function.result
share/mysql-test/suite/engines/funcs/r/tc_partition_key.result
share/mysql-test/suite/engines/funcs/r/tc_partition_linear_key.result
share/mysql-test/suite/engines/funcs/r/tc_partition_list_directory.result
share/mysql-test/suite/engines/funcs/r/tc_partition_list_error.result
share/mysql-test/suite/engines/funcs/r/tc_partition_optimize.result
share/mysql-test/suite/engines/funcs/r/tc_partition_rebuild.result
share/mysql-test/suite/engines/funcs/r/tc_partition_remove.result
share/mysql-test/suite/engines/funcs/r/tc_partition_reorg_divide.result
share/mysql-test/suite/engines/funcs/r/tc_partition_reorg_hash_key.result
share/mysql-test/suite/engines/funcs/r/tc_partition_reorg_merge.result
share/mysql-test/suite/engines/funcs/r/tc_partition_repair.result
share/mysql-test/suite/engines/funcs/r/tc_partition_sub1.result
share/mysql-test/suite/engines/funcs/r/tc_partition_sub2.result
share/mysql-test/suite/engines/funcs/r/tc_partition_value.result
share/mysql-test/suite/engines/funcs/r/tc_partition_value_error.result
share/mysql-test/suite/engines/funcs/r/tc_partition_value_specific.result
share/mysql-test/suite/engines/funcs/r/tc_rename.result
share/mysql-test/suite/engines/funcs/r/tc_rename_across_database.result
share/mysql-test/suite/engines/funcs/r/tc_rename_error.result
share/mysql-test/suite/engines/funcs/r/tc_structure_comment.result
share/mysql-test/suite/engines/funcs/r/tc_structure_create_like.result
share/mysql-test/suite/engines/funcs/r/tc_structure_create_like_string.result
share/mysql-test/suite/engines/funcs/r/tc_structure_create_select.result
share/mysql-test/suite/engines/funcs/r/tc_structure_create_select_string.result
share/mysql-test/suite/engines/funcs/r/tc_structure_string_comment.result
share/mysql-test/suite/engines/funcs/r/tc_temporary_column.result
share/mysql-test/suite/engines/funcs/r/tc_temporary_column_length.result
share/mysql-test/suite/engines/funcs/r/time_function.result
share/mysql-test/suite/engines/funcs/r/tr_all_type_triggers.result
share/mysql-test/suite/engines/funcs/r/tr_delete.result
share/mysql-test/suite/engines/funcs/r/tr_delete_new_error.result
share/mysql-test/suite/engines/funcs/r/tr_insert.result
share/mysql-test/suite/engines/funcs/r/tr_insert_after_error.result
share/mysql-test/suite/engines/funcs/r/tr_insert_old_error.result
share/mysql-test/suite/engines/funcs/r/tr_update.result
share/mysql-test/suite/engines/funcs/r/tr_update_after_error.result
share/mysql-test/suite/engines/funcs/r/up_calendar_range.result
share/mysql-test/suite/engines/funcs/r/up_ignore.result
share/mysql-test/suite/engines/funcs/r/up_limit.result
share/mysql-test/suite/engines/funcs/r/up_multi_db_table.result
share/mysql-test/suite/engines/funcs/r/up_multi_table.result
share/mysql-test/suite/engines/funcs/r/up_nullcheck.result
share/mysql-test/suite/engines/funcs/r/up_number_range.result
share/mysql-test/suite/engines/funcs/r/up_string_range.result
share/mysql-test/suite/engines/funcs/t/ai_init_alter_table.test
share/mysql-test/suite/engines/funcs/t/ai_init_create_table.test
share/mysql-test/suite/engines/funcs/t/ai_init_insert.test
share/mysql-test/suite/engines/funcs/t/ai_init_insert_id.test
share/mysql-test/suite/engines/funcs/t/ai_overflow_error.test
share/mysql-test/suite/engines/funcs/t/ai_reset_by_truncate.test
share/mysql-test/suite/engines/funcs/t/ai_sql_auto_is_null.test
share/mysql-test/suite/engines/funcs/t/an_calendar.test
share/mysql-test/suite/engines/funcs/t/an_number.test
share/mysql-test/suite/engines/funcs/t/an_string.test
share/mysql-test/suite/engines/funcs/t/comment_column.test
share/mysql-test/suite/engines/funcs/t/comment_column2.test
share/mysql-test/suite/engines/funcs/t/comment_table.test
share/mysql-test/suite/engines/funcs/t/crash_manycolumns_number.test
share/mysql-test/suite/engines/funcs/t/crash_manycolumns_string.test
share/mysql-test/suite/engines/funcs/t/crash_manyindexes_number.test
share/mysql-test/suite/engines/funcs/t/crash_manyindexes_string.test
share/mysql-test/suite/engines/funcs/t/crash_manytables_number.test
share/mysql-test/suite/engines/funcs/t/crash_manytables_string.test
share/mysql-test/suite/engines/funcs/t/data1.inc
share/mysql-test/suite/engines/funcs/t/data2.inc
share/mysql-test/suite/engines/funcs/t/date_function.test
share/mysql-test/suite/engines/funcs/t/datetime_function.test
share/mysql-test/suite/engines/funcs/t/db_alter_character_set.test
share/mysql-test/suite/engines/funcs/t/db_alter_character_set_collate.test
share/mysql-test/suite/engines/funcs/t/db_alter_collate_ascii.test
share/mysql-test/suite/engines/funcs/t/db_alter_collate_utf8.test
share/mysql-test/suite/engines/funcs/t/db_create_character_set.test
share/mysql-test/suite/engines/funcs/t/db_create_character_set_collate.test
share/mysql-test/suite/engines/funcs/t/db_create_drop.test
share/mysql-test/suite/engines/funcs/t/db_create_error.test
share/mysql-test/suite/engines/funcs/t/db_create_error_reserved.test
share/mysql-test/suite/engines/funcs/t/db_create_if_not_exists.test
share/mysql-test/suite/engines/funcs/t/db_drop_error.test
share/mysql-test/suite/engines/funcs/t/db_use_error.test
share/mysql-test/suite/engines/funcs/t/de_autoinc.test
share/mysql-test/suite/engines/funcs/t/de_calendar_range.test
share/mysql-test/suite/engines/funcs/t/de_ignore.test
share/mysql-test/suite/engines/funcs/t/de_limit.test
share/mysql-test/suite/engines/funcs/t/de_multi_db_table.test
share/mysql-test/suite/engines/funcs/t/de_multi_db_table_using.test
share/mysql-test/suite/engines/funcs/t/de_multi_table.test
share/mysql-test/suite/engines/funcs/t/de_multi_table_using.test
share/mysql-test/suite/engines/funcs/t/de_number_range.test
share/mysql-test/suite/engines/funcs/t/de_quick.test
share/mysql-test/suite/engines/funcs/t/de_string_range.test
share/mysql-test/suite/engines/funcs/t/de_truncate.test
share/mysql-test/suite/engines/funcs/t/de_truncate_autoinc.test
share/mysql-test/suite/engines/funcs/t/disabled.def
share/mysql-test/suite/engines/funcs/t/fu_aggregate_avg_number.test
share/mysql-test/suite/engines/funcs/t/fu_aggregate_count_number.test
share/mysql-test/suite/engines/funcs/t/fu_aggregate_max_number.test
share/mysql-test/suite/engines/funcs/t/fu_aggregate_max_subquery.test
share/mysql-test/suite/engines/funcs/t/fu_aggregate_min_number.test
share/mysql-test/suite/engines/funcs/t/fu_aggregate_sum_number.test
share/mysql-test/suite/engines/funcs/t/general_no_data.test
share/mysql-test/suite/engines/funcs/t/general_not_null.test
share/mysql-test/suite/engines/funcs/t/general_null.test
share/mysql-test/suite/engines/funcs/t/in_calendar_2_unique_constraints_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_calendar_pk_constraint_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_calendar_pk_constraint_error.test
share/mysql-test/suite/engines/funcs/t/in_calendar_pk_constraint_ignore.test
share/mysql-test/suite/engines/funcs/t/in_calendar_unique_constraint_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_calendar_unique_constraint_error.test
share/mysql-test/suite/engines/funcs/t/in_calendar_unique_constraint_ignore.test
share/mysql-test/suite/engines/funcs/t/in_enum_null.test
share/mysql-test/suite/engines/funcs/t/in_enum_null_boundary_error.test
share/mysql-test/suite/engines/funcs/t/in_enum_null_large_error.test
share/mysql-test/suite/engines/funcs/t/in_insert_select.test
share/mysql-test/suite/engines/funcs/t/in_insert_select_autoinc.test
share/mysql-test/suite/engines/funcs/t/in_insert_select_unique_violation.test
share/mysql-test/suite/engines/funcs/t/in_lob_boundary_error.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_calendar_pk_constraint_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_calendar_pk_constraint_error.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_calendar_pk_constraint_ignore.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_calendar_unique_constraint_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_calendar_unique_constraint_error.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_calendar_unique_constraint_ignore.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_number_pk_constraint_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_number_pk_constraint_error.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_number_pk_constraint_ignore.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_number_unique_constraint_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_number_unique_constraint_error.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_number_unique_constraint_ignore.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_string_pk_constraint_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_string_pk_constraint_error.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_string_pk_constraint_ignore.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_string_unique_constraint_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_string_unique_constraint_error.test
share/mysql-test/suite/engines/funcs/t/in_multicolumn_string_unique_constraint_ignore.test
share/mysql-test/suite/engines/funcs/t/in_number_2_unique_constraints_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_number_boundary_error.test
share/mysql-test/suite/engines/funcs/t/in_number_decimal_boundary_error.test
share/mysql-test/suite/engines/funcs/t/in_number_length.test
share/mysql-test/suite/engines/funcs/t/in_number_null.test
share/mysql-test/suite/engines/funcs/t/in_number_pk_constraint_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_number_pk_constraint_error.test
share/mysql-test/suite/engines/funcs/t/in_number_pk_constraint_ignore.test
share/mysql-test/suite/engines/funcs/t/in_number_unique_constraint_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_number_unique_constraint_error.test
share/mysql-test/suite/engines/funcs/t/in_number_unique_constraint_ignore.test
share/mysql-test/suite/engines/funcs/t/in_set_null.test
share/mysql-test/suite/engines/funcs/t/in_set_null_boundary_error.test
share/mysql-test/suite/engines/funcs/t/in_set_null_large.test
share/mysql-test/suite/engines/funcs/t/in_string_2_unique_constraints_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_string_boundary_error.test
share/mysql-test/suite/engines/funcs/t/in_string_not_null.test
share/mysql-test/suite/engines/funcs/t/in_string_null.test
share/mysql-test/suite/engines/funcs/t/in_string_pk_constraint_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_string_pk_constraint_error.test
share/mysql-test/suite/engines/funcs/t/in_string_pk_constraint_ignore.test
share/mysql-test/suite/engines/funcs/t/in_string_set_enum_fail.test
share/mysql-test/suite/engines/funcs/t/in_string_unique_constraint_duplicate_update.test
share/mysql-test/suite/engines/funcs/t/in_string_unique_constraint_error.test
share/mysql-test/suite/engines/funcs/t/in_string_unique_constraint_ignore.test
share/mysql-test/suite/engines/funcs/t/ix_drop.test
share/mysql-test/suite/engines/funcs/t/ix_drop_error.test
share/mysql-test/suite/engines/funcs/t/ix_index_decimals.test
share/mysql-test/suite/engines/funcs/t/ix_index_lob.test
share/mysql-test/suite/engines/funcs/t/ix_index_non_string.test
share/mysql-test/suite/engines/funcs/t/ix_index_string.test
share/mysql-test/suite/engines/funcs/t/ix_index_string_length.test
share/mysql-test/suite/engines/funcs/t/ix_unique_decimals.test
share/mysql-test/suite/engines/funcs/t/ix_unique_lob.test
share/mysql-test/suite/engines/funcs/t/ix_unique_non_string.test
share/mysql-test/suite/engines/funcs/t/ix_unique_string.test
share/mysql-test/suite/engines/funcs/t/ix_unique_string_length.test
share/mysql-test/suite/engines/funcs/t/ix_using_order.test
share/mysql-test/suite/engines/funcs/t/jp_comment_column.test
share/mysql-test/suite/engines/funcs/t/jp_comment_older_compatibility1.test
share/mysql-test/suite/engines/funcs/t/jp_comment_table.test
share/mysql-test/suite/engines/funcs/t/ld_all_number_string_calendar_types.test
share/mysql-test/suite/engines/funcs/t/ld_bit.test
share/mysql-test/suite/engines/funcs/t/ld_enum_set.test
share/mysql-test/suite/engines/funcs/t/ld_less_columns.test
share/mysql-test/suite/engines/funcs/t/ld_more_columns_truncated.test
share/mysql-test/suite/engines/funcs/t/ld_null.test
share/mysql-test/suite/engines/funcs/t/ld_quote.test
share/mysql-test/suite/engines/funcs/t/ld_simple.test
share/mysql-test/suite/engines/funcs/t/ld_starting.test
share/mysql-test/suite/engines/funcs/t/ld_unique_error1.test
share/mysql-test/suite/engines/funcs/t/ld_unique_error1_local.test
share/mysql-test/suite/engines/funcs/t/ld_unique_error2.test
share/mysql-test/suite/engines/funcs/t/ld_unique_error2_local.test
share/mysql-test/suite/engines/funcs/t/ld_unique_error3.test
share/mysql-test/suite/engines/funcs/t/ld_unique_error3_local.test
share/mysql-test/suite/engines/funcs/t/load_bit.inc
share/mysql-test/suite/engines/funcs/t/load_enum_set.inc
share/mysql-test/suite/engines/funcs/t/load_less_columns.inc
share/mysql-test/suite/engines/funcs/t/load_more_columns.inc
share/mysql-test/suite/engines/funcs/t/load_null.inc
share/mysql-test/suite/engines/funcs/t/load_null2.inc
share/mysql-test/suite/engines/funcs/t/load_quote.inc
share/mysql-test/suite/engines/funcs/t/load_simple.inc
share/mysql-test/suite/engines/funcs/t/load_starting.inc
share/mysql-test/suite/engines/funcs/t/load_unique_error1.inc
share/mysql-test/suite/engines/funcs/t/load_unique_error2.inc
share/mysql-test/suite/engines/funcs/t/load_unique_error3.inc
share/mysql-test/suite/engines/funcs/t/ps_number_length.test
share/mysql-test/suite/engines/funcs/t/ps_number_null.test
share/mysql-test/suite/engines/funcs/t/ps_string_not_null.test
share/mysql-test/suite/engines/funcs/t/ps_string_null.test
share/mysql-test/suite/engines/funcs/t/re_number_range.test
share/mysql-test/suite/engines/funcs/t/re_number_range_set.test
share/mysql-test/suite/engines/funcs/t/re_number_select.test
share/mysql-test/suite/engines/funcs/t/re_string_range.test
share/mysql-test/suite/engines/funcs/t/re_string_range_set.test
share/mysql-test/suite/engines/funcs/t/rpl000010-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl000010.test
share/mysql-test/suite/engines/funcs/t/rpl000011.test
share/mysql-test/suite/engines/funcs/t/rpl000013.test
share/mysql-test/suite/engines/funcs/t/rpl000017-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl000017.test
share/mysql-test/suite/engines/funcs/t/rpl_000015.test
share/mysql-test/suite/engines/funcs/t/rpl_LD_INFILE.test
share/mysql-test/suite/engines/funcs/t/rpl_REDIRECT.test
share/mysql-test/suite/engines/funcs/t/rpl_alter.test
share/mysql-test/suite/engines/funcs/t/rpl_alter_db.test
share/mysql-test/suite/engines/funcs/t/rpl_bit.test
share/mysql-test/suite/engines/funcs/t/rpl_bit_npk.test
share/mysql-test/suite/engines/funcs/t/rpl_change_master.test
share/mysql-test/suite/engines/funcs/t/rpl_create_database-master.opt
share/mysql-test/suite/engines/funcs/t/rpl_create_database-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_create_database.test
share/mysql-test/suite/engines/funcs/t/rpl_do_grant.test
share/mysql-test/suite/engines/funcs/t/rpl_drop.test
share/mysql-test/suite/engines/funcs/t/rpl_drop_db.test
share/mysql-test/suite/engines/funcs/t/rpl_dual_pos_advance-master.opt
share/mysql-test/suite/engines/funcs/t/rpl_dual_pos_advance.test
share/mysql-test/suite/engines/funcs/t/rpl_empty_master_crash-master.opt
share/mysql-test/suite/engines/funcs/t/rpl_empty_master_crash.test
share/mysql-test/suite/engines/funcs/t/rpl_err_ignoredtable-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_err_ignoredtable.test
share/mysql-test/suite/engines/funcs/t/rpl_flushlog_loop.test
share/mysql-test/suite/engines/funcs/t/rpl_free_items-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_free_items.test
share/mysql-test/suite/engines/funcs/t/rpl_get_lock.test
share/mysql-test/suite/engines/funcs/t/rpl_ignore_grant-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_ignore_grant.test
share/mysql-test/suite/engines/funcs/t/rpl_ignore_revoke-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_ignore_revoke.test
share/mysql-test/suite/engines/funcs/t/rpl_ignore_table_update-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_ignore_table_update.test
share/mysql-test/suite/engines/funcs/t/rpl_init_slave-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_init_slave.test
share/mysql-test/suite/engines/funcs/t/rpl_insert.test
share/mysql-test/suite/engines/funcs/t/rpl_insert_select.test
share/mysql-test/suite/engines/funcs/t/rpl_loaddata2.test
share/mysql-test/suite/engines/funcs/t/rpl_loaddata_m-master.opt
share/mysql-test/suite/engines/funcs/t/rpl_loaddata_m.test
share/mysql-test/suite/engines/funcs/t/rpl_loaddata_s-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_loaddata_s.test
share/mysql-test/suite/engines/funcs/t/rpl_loaddatalocal.test
share/mysql-test/suite/engines/funcs/t/rpl_loadfile.test
share/mysql-test/suite/engines/funcs/t/rpl_log_pos.test
share/mysql-test/suite/engines/funcs/t/rpl_many_optimize.test
share/mysql-test/suite/engines/funcs/t/rpl_master_pos_wait.test
share/mysql-test/suite/engines/funcs/t/rpl_misc_functions.test
share/mysql-test/suite/engines/funcs/t/rpl_multi_delete-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_multi_delete.test
share/mysql-test/suite/engines/funcs/t/rpl_multi_delete2-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_multi_delete2.test
share/mysql-test/suite/engines/funcs/t/rpl_multi_update4-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_multi_update4.test
share/mysql-test/suite/engines/funcs/t/rpl_ps.test
share/mysql-test/suite/engines/funcs/t/rpl_rbr_to_sbr.test
share/mysql-test/suite/engines/funcs/t/rpl_relayspace-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_relayspace.test
share/mysql-test/suite/engines/funcs/t/rpl_replicate_ignore_db-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_replicate_ignore_db.test
share/mysql-test/suite/engines/funcs/t/rpl_row_NOW.test
share/mysql-test/suite/engines/funcs/t/rpl_row_USER.test
share/mysql-test/suite/engines/funcs/t/rpl_row_drop.test
share/mysql-test/suite/engines/funcs/t/rpl_row_func001.test
share/mysql-test/suite/engines/funcs/t/rpl_row_inexist_tbl-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_row_inexist_tbl.test
share/mysql-test/suite/engines/funcs/t/rpl_row_max_relay_size.test
share/mysql-test/suite/engines/funcs/t/rpl_row_reset_slave.test
share/mysql-test/suite/engines/funcs/t/rpl_row_sp001.test
share/mysql-test/suite/engines/funcs/t/rpl_row_sp005.test
share/mysql-test/suite/engines/funcs/t/rpl_row_sp008.test
share/mysql-test/suite/engines/funcs/t/rpl_row_sp009.test
share/mysql-test/suite/engines/funcs/t/rpl_row_sp010.test
share/mysql-test/suite/engines/funcs/t/rpl_row_sp011.test
share/mysql-test/suite/engines/funcs/t/rpl_row_sp012.test
share/mysql-test/suite/engines/funcs/t/rpl_row_stop_middle.test
share/mysql-test/suite/engines/funcs/t/rpl_row_trig001.test
share/mysql-test/suite/engines/funcs/t/rpl_row_trig002.test
share/mysql-test/suite/engines/funcs/t/rpl_row_trig003.test
share/mysql-test/suite/engines/funcs/t/rpl_row_until.test
share/mysql-test/suite/engines/funcs/t/rpl_row_view01.test
share/mysql-test/suite/engines/funcs/t/rpl_server_id1.test
share/mysql-test/suite/engines/funcs/t/rpl_server_id2-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_server_id2.test
share/mysql-test/suite/engines/funcs/t/rpl_session_var.test
share/mysql-test/suite/engines/funcs/t/rpl_sf.test
share/mysql-test/suite/engines/funcs/t/rpl_skip_error-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_skip_error.test
share/mysql-test/suite/engines/funcs/t/rpl_slave_status.test
share/mysql-test/suite/engines/funcs/t/rpl_sp-master.opt
share/mysql-test/suite/engines/funcs/t/rpl_sp-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_sp.test
share/mysql-test/suite/engines/funcs/t/rpl_sp004.test
share/mysql-test/suite/engines/funcs/t/rpl_sp_effects-master.opt
share/mysql-test/suite/engines/funcs/t/rpl_sp_effects-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_sp_effects.test
share/mysql-test/suite/engines/funcs/t/rpl_start_stop_slave.test
share/mysql-test/suite/engines/funcs/t/rpl_stm_max_relay_size.test
share/mysql-test/suite/engines/funcs/t/rpl_stm_mystery22.test
share/mysql-test/suite/engines/funcs/t/rpl_stm_no_op.test
share/mysql-test/suite/engines/funcs/t/rpl_stm_reset_slave.test
share/mysql-test/suite/engines/funcs/t/rpl_switch_stm_row_mixed.test
share/mysql-test/suite/engines/funcs/t/rpl_temp_table.test
share/mysql-test/suite/engines/funcs/t/rpl_temporary.test
share/mysql-test/suite/engines/funcs/t/rpl_trigger.test
share/mysql-test/suite/engines/funcs/t/rpl_trunc_temp.test
share/mysql-test/suite/engines/funcs/t/rpl_user_variables.test
share/mysql-test/suite/engines/funcs/t/rpl_variables-master.opt
share/mysql-test/suite/engines/funcs/t/rpl_variables.test
share/mysql-test/suite/engines/funcs/t/rpl_view-slave.opt
share/mysql-test/suite/engines/funcs/t/rpl_view.test
share/mysql-test/suite/engines/funcs/t/se_join_cross.test
share/mysql-test/suite/engines/funcs/t/se_join_default.test
share/mysql-test/suite/engines/funcs/t/se_join_inner.test
share/mysql-test/suite/engines/funcs/t/se_join_left.test
share/mysql-test/suite/engines/funcs/t/se_join_left_outer.test
share/mysql-test/suite/engines/funcs/t/se_join_natural_left.test
share/mysql-test/suite/engines/funcs/t/se_join_natural_left_outer.test
share/mysql-test/suite/engines/funcs/t/se_join_natural_right.test
share/mysql-test/suite/engines/funcs/t/se_join_natural_right_outer.test
share/mysql-test/suite/engines/funcs/t/se_join_right.test
share/mysql-test/suite/engines/funcs/t/se_join_right_outer.test
share/mysql-test/suite/engines/funcs/t/se_join_straight.test
share/mysql-test/suite/engines/funcs/t/se_rowid.test
share/mysql-test/suite/engines/funcs/t/se_string_distinct.test
share/mysql-test/suite/engines/funcs/t/se_string_from.test
share/mysql-test/suite/engines/funcs/t/se_string_groupby.test
share/mysql-test/suite/engines/funcs/t/se_string_having.test
share/mysql-test/suite/engines/funcs/t/se_string_limit.test
share/mysql-test/suite/engines/funcs/t/se_string_orderby.test
share/mysql-test/suite/engines/funcs/t/se_string_union.test
share/mysql-test/suite/engines/funcs/t/se_string_where.test
share/mysql-test/suite/engines/funcs/t/se_string_where_and.test
share/mysql-test/suite/engines/funcs/t/se_string_where_or.test
share/mysql-test/suite/engines/funcs/t/sf_alter.test
share/mysql-test/suite/engines/funcs/t/sf_cursor.test
share/mysql-test/suite/engines/funcs/t/sf_simple1.test
share/mysql-test/suite/engines/funcs/t/sp_alter.test
share/mysql-test/suite/engines/funcs/t/sp_cursor.test
share/mysql-test/suite/engines/funcs/t/sp_simple1.test
share/mysql-test/suite/engines/funcs/t/sq_all.test
share/mysql-test/suite/engines/funcs/t/sq_any.test
share/mysql-test/suite/engines/funcs/t/sq_corr.test
share/mysql-test/suite/engines/funcs/t/sq_error.test
share/mysql-test/suite/engines/funcs/t/sq_exists.test
share/mysql-test/suite/engines/funcs/t/sq_from.test
share/mysql-test/suite/engines/funcs/t/sq_in.test
share/mysql-test/suite/engines/funcs/t/sq_row.test
share/mysql-test/suite/engines/funcs/t/sq_scalar.test
share/mysql-test/suite/engines/funcs/t/sq_some.test
share/mysql-test/suite/engines/funcs/t/ta_2part_column_to_pk.test
share/mysql-test/suite/engines/funcs/t/ta_2part_diff_string_to_pk.test
share/mysql-test/suite/engines/funcs/t/ta_2part_diff_to_pk.test
share/mysql-test/suite/engines/funcs/t/ta_2part_string_to_pk.test
share/mysql-test/suite/engines/funcs/t/ta_3part_column_to_pk.test
share/mysql-test/suite/engines/funcs/t/ta_3part_string_to_pk.test
share/mysql-test/suite/engines/funcs/t/ta_add_column.test
share/mysql-test/suite/engines/funcs/t/ta_add_column2.test
share/mysql-test/suite/engines/funcs/t/ta_add_column_first.test
share/mysql-test/suite/engines/funcs/t/ta_add_column_first2.test
share/mysql-test/suite/engines/funcs/t/ta_add_column_middle.test
share/mysql-test/suite/engines/funcs/t/ta_add_column_middle2.test
share/mysql-test/suite/engines/funcs/t/ta_add_string.test
share/mysql-test/suite/engines/funcs/t/ta_add_string2.test
share/mysql-test/suite/engines/funcs/t/ta_add_string_first.test
share/mysql-test/suite/engines/funcs/t/ta_add_string_first2.test
share/mysql-test/suite/engines/funcs/t/ta_add_string_middle.test
share/mysql-test/suite/engines/funcs/t/ta_add_string_middle2.test
share/mysql-test/suite/engines/funcs/t/ta_add_string_unique_index.test
share/mysql-test/suite/engines/funcs/t/ta_add_unique_index.test
share/mysql-test/suite/engines/funcs/t/ta_column_from_unsigned.test
share/mysql-test/suite/engines/funcs/t/ta_column_from_zerofill.test
share/mysql-test/suite/engines/funcs/t/ta_column_to_index.test
share/mysql-test/suite/engines/funcs/t/ta_column_to_not_null.test
share/mysql-test/suite/engines/funcs/t/ta_column_to_null.test
share/mysql-test/suite/engines/funcs/t/ta_column_to_pk.test
share/mysql-test/suite/engines/funcs/t/ta_column_to_unsigned.test
share/mysql-test/suite/engines/funcs/t/ta_column_to_zerofill.test
share/mysql-test/suite/engines/funcs/t/ta_drop_column.test
share/mysql-test/suite/engines/funcs/t/ta_drop_index.test
share/mysql-test/suite/engines/funcs/t/ta_drop_pk_autoincrement.test
share/mysql-test/suite/engines/funcs/t/ta_drop_pk_number.test
share/mysql-test/suite/engines/funcs/t/ta_drop_pk_string.test
share/mysql-test/suite/engines/funcs/t/ta_drop_string_index.test
share/mysql-test/suite/engines/funcs/t/ta_orderby.test
share/mysql-test/suite/engines/funcs/t/ta_rename.test
share/mysql-test/suite/engines/funcs/t/ta_set_drop_default.test
share/mysql-test/suite/engines/funcs/t/ta_string_drop_column.test
share/mysql-test/suite/engines/funcs/t/ta_string_to_index.test
share/mysql-test/suite/engines/funcs/t/ta_string_to_not_null.test
share/mysql-test/suite/engines/funcs/t/ta_string_to_null.test
share/mysql-test/suite/engines/funcs/t/ta_string_to_pk.test
share/mysql-test/suite/engines/funcs/t/tc_column_autoincrement.test
share/mysql-test/suite/engines/funcs/t/tc_column_comment.test
share/mysql-test/suite/engines/funcs/t/tc_column_comment_string.test
share/mysql-test/suite/engines/funcs/t/tc_column_default_decimal.test
share/mysql-test/suite/engines/funcs/t/tc_column_default_number.test
share/mysql-test/suite/engines/funcs/t/tc_column_default_string.test
share/mysql-test/suite/engines/funcs/t/tc_column_enum.test
share/mysql-test/suite/engines/funcs/t/tc_column_enum_long.test
share/mysql-test/suite/engines/funcs/t/tc_column_key.test
share/mysql-test/suite/engines/funcs/t/tc_column_key_length.test
share/mysql-test/suite/engines/funcs/t/tc_column_length.test
share/mysql-test/suite/engines/funcs/t/tc_column_length_decimals.test
share/mysql-test/suite/engines/funcs/t/tc_column_length_zero.test
share/mysql-test/suite/engines/funcs/t/tc_column_not_null.test
share/mysql-test/suite/engines/funcs/t/tc_column_null.test
share/mysql-test/suite/engines/funcs/t/tc_column_primary_key_number.test
share/mysql-test/suite/engines/funcs/t/tc_column_primary_key_string.test
share/mysql-test/suite/engines/funcs/t/tc_column_serial.test
share/mysql-test/suite/engines/funcs/t/tc_column_set.test
share/mysql-test/suite/engines/funcs/t/tc_column_set_long.test
share/mysql-test/suite/engines/funcs/t/tc_column_unique_key.test
share/mysql-test/suite/engines/funcs/t/tc_column_unique_key_string.test
share/mysql-test/suite/engines/funcs/t/tc_column_unsigned.test
share/mysql-test/suite/engines/funcs/t/tc_column_zerofill.test
share/mysql-test/suite/engines/funcs/t/tc_drop_table.test
share/mysql-test/suite/engines/funcs/t/tc_multicolumn_different.test
share/mysql-test/suite/engines/funcs/t/tc_multicolumn_same.test
share/mysql-test/suite/engines/funcs/t/tc_multicolumn_same_string.test
share/mysql-test/suite/engines/funcs/t/tc_partition_analyze.test
share/mysql-test/suite/engines/funcs/t/tc_partition_change_from_range_to_hash_key.test
share/mysql-test/suite/engines/funcs/t/tc_partition_check.test
share/mysql-test/suite/engines/funcs/t/tc_partition_hash.test
share/mysql-test/suite/engines/funcs/t/tc_partition_hash_date_function.test
share/mysql-test/suite/engines/funcs/t/tc_partition_key.test
share/mysql-test/suite/engines/funcs/t/tc_partition_linear_key.test
share/mysql-test/suite/engines/funcs/t/tc_partition_list_directory.test
share/mysql-test/suite/engines/funcs/t/tc_partition_list_error.test
share/mysql-test/suite/engines/funcs/t/tc_partition_optimize.test
share/mysql-test/suite/engines/funcs/t/tc_partition_rebuild.test
share/mysql-test/suite/engines/funcs/t/tc_partition_remove.test
share/mysql-test/suite/engines/funcs/t/tc_partition_reorg_divide.test
share/mysql-test/suite/engines/funcs/t/tc_partition_reorg_hash_key.test
share/mysql-test/suite/engines/funcs/t/tc_partition_reorg_merge.test
share/mysql-test/suite/engines/funcs/t/tc_partition_repair.test
share/mysql-test/suite/engines/funcs/t/tc_partition_sub1.test
share/mysql-test/suite/engines/funcs/t/tc_partition_sub2.test
share/mysql-test/suite/engines/funcs/t/tc_partition_value.test
share/mysql-test/suite/engines/funcs/t/tc_partition_value_error.test
share/mysql-test/suite/engines/funcs/t/tc_partition_value_specific.test
share/mysql-test/suite/engines/funcs/t/tc_rename.test
share/mysql-test/suite/engines/funcs/t/tc_rename_across_database.test
share/mysql-test/suite/engines/funcs/t/tc_rename_error.test
share/mysql-test/suite/engines/funcs/t/tc_structure_comment.test
share/mysql-test/suite/engines/funcs/t/tc_structure_create_like.test
share/mysql-test/suite/engines/funcs/t/tc_structure_create_like_string.test
share/mysql-test/suite/engines/funcs/t/tc_structure_create_select.test
share/mysql-test/suite/engines/funcs/t/tc_structure_create_select_string.test
share/mysql-test/suite/engines/funcs/t/tc_structure_string_comment.test
share/mysql-test/suite/engines/funcs/t/tc_temporary_column.test
share/mysql-test/suite/engines/funcs/t/tc_temporary_column_length.test
share/mysql-test/suite/engines/funcs/t/time_function.test
share/mysql-test/suite/engines/funcs/t/tr_all_type_triggers.test
share/mysql-test/suite/engines/funcs/t/tr_delete.test
share/mysql-test/suite/engines/funcs/t/tr_delete_new_error.test
share/mysql-test/suite/engines/funcs/t/tr_insert.test
share/mysql-test/suite/engines/funcs/t/tr_insert_after_error.test
share/mysql-test/suite/engines/funcs/t/tr_insert_old_error.test
share/mysql-test/suite/engines/funcs/t/tr_update.test
share/mysql-test/suite/engines/funcs/t/tr_update_after_error.test
share/mysql-test/suite/engines/funcs/t/up_calendar_range.test
share/mysql-test/suite/engines/funcs/t/up_ignore.test
share/mysql-test/suite/engines/funcs/t/up_limit.test
share/mysql-test/suite/engines/funcs/t/up_multi_db_table.test
share/mysql-test/suite/engines/funcs/t/up_multi_table.test
share/mysql-test/suite/engines/funcs/t/up_nullcheck.test
share/mysql-test/suite/engines/funcs/t/up_number_range.test
share/mysql-test/suite/engines/funcs/t/up_string_range.test
share/mysql-test/suite/engines/funcs/t/wait_show_pattern.inc
share/mysql-test/suite/engines/funcs/t/wait_slave_status.inc
share/mysql-test/suite/engines/iuds/r/delete_decimal.result
share/mysql-test/suite/engines/iuds/r/delete_time.result
share/mysql-test/suite/engines/iuds/r/delete_year.result
share/mysql-test/suite/engines/iuds/r/insert_calendar.result
share/mysql-test/suite/engines/iuds/r/insert_decimal.result
share/mysql-test/suite/engines/iuds/r/insert_number.result
share/mysql-test/suite/engines/iuds/r/insert_time.result
share/mysql-test/suite/engines/iuds/r/insert_year.result
share/mysql-test/suite/engines/iuds/r/strings_charsets_update_delete.result
share/mysql-test/suite/engines/iuds/r/strings_update_delete.result
share/mysql-test/suite/engines/iuds/r/type_bit_iuds.result
share/mysql-test/suite/engines/iuds/r/update_decimal.result
share/mysql-test/suite/engines/iuds/r/update_delete_calendar.result
share/mysql-test/suite/engines/iuds/r/update_delete_number.result
share/mysql-test/suite/engines/iuds/r/update_time.result
share/mysql-test/suite/engines/iuds/r/update_year.result
share/mysql-test/suite/engines/iuds/t/delete_decimal.test
share/mysql-test/suite/engines/iuds/t/delete_time.test
share/mysql-test/suite/engines/iuds/t/delete_year.test
share/mysql-test/suite/engines/iuds/t/disabled.def
share/mysql-test/suite/engines/iuds/t/hindi.txt
share/mysql-test/suite/engines/iuds/t/insert_calendar.test
share/mysql-test/suite/engines/iuds/t/insert_decimal.test
share/mysql-test/suite/engines/iuds/t/insert_number.test
share/mysql-test/suite/engines/iuds/t/insert_time.test
share/mysql-test/suite/engines/iuds/t/insert_year.test
share/mysql-test/suite/engines/iuds/t/sample.txt
share/mysql-test/suite/engines/iuds/t/strings_charsets_update_delete.test
share/mysql-test/suite/engines/iuds/t/strings_update_delete.test
share/mysql-test/suite/engines/iuds/t/type_bit_iuds.test
share/mysql-test/suite/engines/iuds/t/update_decimal.test
share/mysql-test/suite/engines/iuds/t/update_delete_calendar.test
share/mysql-test/suite/engines/iuds/t/update_delete_number.test
share/mysql-test/suite/engines/iuds/t/update_time.test
share/mysql-test/suite/engines/iuds/t/update_year.test
share/mysql-test/suite/engines/rr_trx/check_consistency.sql
share/mysql-test/suite/engines/rr_trx/include/check_for_error_rollback.inc
share/mysql-test/suite/engines/rr_trx/include/check_for_error_rollback_skip.inc
share/mysql-test/suite/engines/rr_trx/include/check_repeatable_read_all_columns.inc
share/mysql-test/suite/engines/rr_trx/include/record_query_all_columns.inc
share/mysql-test/suite/engines/rr_trx/include/rr_init.test
share/mysql-test/suite/engines/rr_trx/init_innodb.txt
share/mysql-test/suite/engines/rr_trx/r/init_innodb.result
share/mysql-test/suite/engines/rr_trx/r/rr_c_count_not_zero.result
share/mysql-test/suite/engines/rr_trx/r/rr_c_stats.result
share/mysql-test/suite/engines/rr_trx/r/rr_i_40-44.result
share/mysql-test/suite/engines/rr_trx/r/rr_id_3.result
share/mysql-test/suite/engines/rr_trx/r/rr_id_900.result
share/mysql-test/suite/engines/rr_trx/r/rr_insert_select_2.result
share/mysql-test/suite/engines/rr_trx/r/rr_iud_rollback-multi-50.result
share/mysql-test/suite/engines/rr_trx/r/rr_replace_7-8.result
share/mysql-test/suite/engines/rr_trx/r/rr_s_select-uncommitted.result
share/mysql-test/suite/engines/rr_trx/r/rr_sc_select-limit-nolimit_4.result
share/mysql-test/suite/engines/rr_trx/r/rr_sc_select-same_2.result
share/mysql-test/suite/engines/rr_trx/r/rr_sc_sum_total.result
share/mysql-test/suite/engines/rr_trx/r/rr_u_10-19.result
share/mysql-test/suite/engines/rr_trx/r/rr_u_10-19_nolimit.result
share/mysql-test/suite/engines/rr_trx/r/rr_u_4.result
share/mysql-test/suite/engines/rr_trx/run.txt
share/mysql-test/suite/engines/rr_trx/run_stress_tx_rr.pl
share/mysql-test/suite/engines/rr_trx/t/init_innodb.test
share/mysql-test/suite/engines/rr_trx/t/rr_c_count_not_zero.test
share/mysql-test/suite/engines/rr_trx/t/rr_c_stats.test
share/mysql-test/suite/engines/rr_trx/t/rr_i_40-44.test
share/mysql-test/suite/engines/rr_trx/t/rr_id_3.test
share/mysql-test/suite/engines/rr_trx/t/rr_id_900.test
share/mysql-test/suite/engines/rr_trx/t/rr_insert_select_2.test
share/mysql-test/suite/engines/rr_trx/t/rr_iud_rollback-multi-50.test
share/mysql-test/suite/engines/rr_trx/t/rr_replace_7-8.test
share/mysql-test/suite/engines/rr_trx/t/rr_s_select-uncommitted.test
share/mysql-test/suite/engines/rr_trx/t/rr_sc_select-limit-nolimit_4.test
share/mysql-test/suite/engines/rr_trx/t/rr_sc_select-same_2.test
share/mysql-test/suite/engines/rr_trx/t/rr_sc_sum_total.test
share/mysql-test/suite/engines/rr_trx/t/rr_u_10-19.test
share/mysql-test/suite/engines/rr_trx/t/rr_u_10-19_nolimit.test
share/mysql-test/suite/engines/rr_trx/t/rr_u_4.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/federated/disabled.def
share/mysql-test/suite/federated/federated.result
share/mysql-test/suite/federated/federated.test
share/mysql-test/suite/federated/federated_archive.result
share/mysql-test/suite/federated/federated_archive.test
share/mysql-test/suite/federated/federated_bug_13118.result
share/mysql-test/suite/federated/federated_bug_13118.test
share/mysql-test/suite/federated/federated_bug_25714.result
share/mysql-test/suite/federated/federated_bug_25714.test
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/federated/federated_bug_35333.result
share/mysql-test/suite/federated/federated_bug_35333.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/federated/federated_debug-master.opt
share/mysql-test/suite/federated/federated_debug.result
share/mysql-test/suite/federated/federated_debug.test
share/mysql-test/suite/federated/federated_innodb-slave.opt
share/mysql-test/suite/federated/federated_innodb.result
share/mysql-test/suite/federated/federated_innodb.test
Changes 5.1.60: * Upgrading from an Advanced GPL RPM package to an Advanced RPM package did not work. Now on Linux it is possible to use rpm -U to replace any installed MySQL product by any other of the same release family. It is not necessary to remove the old produce with rpm -e first. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. Bugs Fixed * Important Change: InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Replication: Issuing the following statements, in the order shown, could cause a deadlock between the user thread and I/O thread. * more...
2011-12-02 15:25:09 +01:00
share/mysql-test/suite/federated/federated_plugin-master.opt
share/mysql-test/suite/federated/federated_plugin.result
share/mysql-test/suite/federated/federated_plugin.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/federated/federated_server.result
share/mysql-test/suite/federated/federated_server.test
share/mysql-test/suite/federated/federated_transactions-slave.opt
share/mysql-test/suite/federated/federated_transactions.result
share/mysql-test/suite/federated/federated_transactions.test
Changes 5.1.67: Bug fixes http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-67.html
2013-01-21 09:58:43 +01:00
share/mysql-test/suite/federated/include/federated.inc
share/mysql-test/suite/federated/include/federated_cleanup.inc
share/mysql-test/suite/federated/include/have_federated_db.inc
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/federated/my.cnf
share/mysql-test/suite/funcs_1/README.txt
share/mysql-test/suite/funcs_1/bitdata/bitdata_master.test
share/mysql-test/suite/funcs_1/cursors/cursors_master.test
share/mysql-test/suite/funcs_1/datadict/basics_mixed1.inc
share/mysql-test/suite/funcs_1/datadict/basics_mixed2.inc
share/mysql-test/suite/funcs_1/datadict/basics_mixed3.inc
share/mysql-test/suite/funcs_1/datadict/columns.inc
share/mysql-test/suite/funcs_1/datadict/datadict.pre
share/mysql-test/suite/funcs_1/datadict/datadict_bug_12777.inc
share/mysql-test/suite/funcs_1/datadict/datadict_load.inc
share/mysql-test/suite/funcs_1/datadict/datadict_priv.inc
share/mysql-test/suite/funcs_1/datadict/is_key_column_usage.inc
share/mysql-test/suite/funcs_1/datadict/is_routines.inc
share/mysql-test/suite/funcs_1/datadict/is_schemata.inc
share/mysql-test/suite/funcs_1/datadict/is_table_query.inc
share/mysql-test/suite/funcs_1/datadict/is_tables.inc
share/mysql-test/suite/funcs_1/datadict/is_triggers.inc
share/mysql-test/suite/funcs_1/datadict/is_views.inc
share/mysql-test/suite/funcs_1/datadict/processlist_priv.inc
share/mysql-test/suite/funcs_1/datadict/processlist_val.inc
share/mysql-test/suite/funcs_1/datadict/statistics.inc
share/mysql-test/suite/funcs_1/datadict/table_constraints.inc
share/mysql-test/suite/funcs_1/datadict/tables.inc
share/mysql-test/suite/funcs_1/datadict/tables1.inc
share/mysql-test/suite/funcs_1/datadict/tables2.inc
share/mysql-test/suite/funcs_1/include/bug28309_skip.inc
share/mysql-test/suite/funcs_1/include/cleanup.inc
share/mysql-test/suite/funcs_1/include/innodb_tb1.inc
share/mysql-test/suite/funcs_1/include/innodb_tb2.inc
share/mysql-test/suite/funcs_1/include/innodb_tb3.inc
share/mysql-test/suite/funcs_1/include/innodb_tb4.inc
share/mysql-test/suite/funcs_1/include/memory_tb1.inc
share/mysql-test/suite/funcs_1/include/memory_tb2.inc
share/mysql-test/suite/funcs_1/include/memory_tb3.inc
share/mysql-test/suite/funcs_1/include/memory_tb4.inc
share/mysql-test/suite/funcs_1/include/myisam_tb1.inc
share/mysql-test/suite/funcs_1/include/myisam_tb2.inc
share/mysql-test/suite/funcs_1/include/myisam_tb3.inc
share/mysql-test/suite/funcs_1/include/myisam_tb4.inc
share/mysql-test/suite/funcs_1/include/ndb_tb1.inc
share/mysql-test/suite/funcs_1/include/ndb_tb2.inc
share/mysql-test/suite/funcs_1/include/ndb_tb3.inc
share/mysql-test/suite/funcs_1/include/ndb_tb4.inc
share/mysql-test/suite/funcs_1/include/show_connection.inc
share/mysql-test/suite/funcs_1/include/sp_tb.inc
share/mysql-test/suite/funcs_1/include/tb3.inc
share/mysql-test/suite/funcs_1/lib/DataGen_local.pl
share/mysql-test/suite/funcs_1/lib/DataGen_modify.pl
share/mysql-test/suite/funcs_1/r/charset_collation.result
share/mysql-test/suite/funcs_1/r/innodb_bitdata.result
share/mysql-test/suite/funcs_1/r/innodb_cursors.result
share/mysql-test/suite/funcs_1/r/innodb_func_view.result
share/mysql-test/suite/funcs_1/r/innodb_storedproc_02.result
share/mysql-test/suite/funcs_1/r/innodb_storedproc_03.result
share/mysql-test/suite/funcs_1/r/innodb_storedproc_06.result
share/mysql-test/suite/funcs_1/r/innodb_storedproc_07.result
share/mysql-test/suite/funcs_1/r/innodb_storedproc_08.result
share/mysql-test/suite/funcs_1/r/innodb_storedproc_10.result
share/mysql-test/suite/funcs_1/r/innodb_trig_0102.result
share/mysql-test/suite/funcs_1/r/innodb_trig_03.result
share/mysql-test/suite/funcs_1/r/innodb_trig_03e.result
share/mysql-test/suite/funcs_1/r/innodb_trig_0407.result
share/mysql-test/suite/funcs_1/r/innodb_trig_08.result
share/mysql-test/suite/funcs_1/r/innodb_trig_09.result
share/mysql-test/suite/funcs_1/r/innodb_trig_1011ext.result
share/mysql-test/suite/funcs_1/r/innodb_trig_frkey.result
share/mysql-test/suite/funcs_1/r/innodb_views.result
share/mysql-test/suite/funcs_1/r/is_basics_mixed.result
share/mysql-test/suite/funcs_1/r/is_character_sets.result
share/mysql-test/suite/funcs_1/r/is_cml_innodb.result
share/mysql-test/suite/funcs_1/r/is_cml_memory.result
share/mysql-test/suite/funcs_1/r/is_cml_myisam.result
share/mysql-test/suite/funcs_1/r/is_cml_ndb.result
share/mysql-test/suite/funcs_1/r/is_coll_char_set_appl.result
share/mysql-test/suite/funcs_1/r/is_collations.result
share/mysql-test/suite/funcs_1/r/is_column_privileges.result
share/mysql-test/suite/funcs_1/r/is_column_privileges_is_mysql_test.result
share/mysql-test/suite/funcs_1/r/is_columns.result
share/mysql-test/suite/funcs_1/r/is_columns_innodb.result
share/mysql-test/suite/funcs_1/r/is_columns_is.result
share/mysql-test/suite/funcs_1/r/is_columns_is_embedded.result
share/mysql-test/suite/funcs_1/r/is_columns_memory.result
share/mysql-test/suite/funcs_1/r/is_columns_myisam.result
share/mysql-test/suite/funcs_1/r/is_columns_myisam_embedded.result
share/mysql-test/suite/funcs_1/r/is_columns_mysql.result
share/mysql-test/suite/funcs_1/r/is_columns_mysql_embedded.result
share/mysql-test/suite/funcs_1/r/is_columns_ndb.result
share/mysql-test/suite/funcs_1/r/is_engines.result
share/mysql-test/suite/funcs_1/r/is_engines_archive.result
share/mysql-test/suite/funcs_1/r/is_engines_blackhole.result
share/mysql-test/suite/funcs_1/r/is_engines_csv.result
share/mysql-test/suite/funcs_1/r/is_engines_federated.result
share/mysql-test/suite/funcs_1/r/is_engines_innodb.result
share/mysql-test/suite/funcs_1/r/is_engines_memory.result
share/mysql-test/suite/funcs_1/r/is_engines_merge.result
share/mysql-test/suite/funcs_1/r/is_engines_myisam.result
share/mysql-test/suite/funcs_1/r/is_engines_ndb.result
share/mysql-test/suite/funcs_1/r/is_events.result
share/mysql-test/suite/funcs_1/r/is_key_column_usage.result
share/mysql-test/suite/funcs_1/r/is_key_column_usage_embedded.result
share/mysql-test/suite/funcs_1/r/is_routines.result
share/mysql-test/suite/funcs_1/r/is_routines_embedded.result
share/mysql-test/suite/funcs_1/r/is_schema_privileges.result
share/mysql-test/suite/funcs_1/r/is_schema_privileges_is_mysql_test.result
share/mysql-test/suite/funcs_1/r/is_schemata.result
share/mysql-test/suite/funcs_1/r/is_schemata_embedded.result
share/mysql-test/suite/funcs_1/r/is_schemata_is_mysql_test.result
share/mysql-test/suite/funcs_1/r/is_statistics.result
share/mysql-test/suite/funcs_1/r/is_statistics_is.result
share/mysql-test/suite/funcs_1/r/is_statistics_mysql.result
share/mysql-test/suite/funcs_1/r/is_statistics_mysql_embedded.result
share/mysql-test/suite/funcs_1/r/is_table_constraints.result
share/mysql-test/suite/funcs_1/r/is_table_constraints_is.result
share/mysql-test/suite/funcs_1/r/is_table_constraints_mysql.result
share/mysql-test/suite/funcs_1/r/is_table_constraints_mysql_embedded.result
share/mysql-test/suite/funcs_1/r/is_table_privileges.result
share/mysql-test/suite/funcs_1/r/is_tables.result
share/mysql-test/suite/funcs_1/r/is_tables_embedded.result
share/mysql-test/suite/funcs_1/r/is_tables_innodb.result
share/mysql-test/suite/funcs_1/r/is_tables_is.result
share/mysql-test/suite/funcs_1/r/is_tables_memory.result
share/mysql-test/suite/funcs_1/r/is_tables_myisam.result
share/mysql-test/suite/funcs_1/r/is_tables_myisam_embedded.result
share/mysql-test/suite/funcs_1/r/is_tables_mysql.result
share/mysql-test/suite/funcs_1/r/is_tables_mysql_embedded.result
share/mysql-test/suite/funcs_1/r/is_tables_ndb.result
share/mysql-test/suite/funcs_1/r/is_triggers.result
share/mysql-test/suite/funcs_1/r/is_triggers_embedded.result
share/mysql-test/suite/funcs_1/r/is_user_privileges.result
share/mysql-test/suite/funcs_1/r/is_views.result
share/mysql-test/suite/funcs_1/r/is_views_embedded.result
share/mysql-test/suite/funcs_1/r/memory_bitdata.result
share/mysql-test/suite/funcs_1/r/memory_cursors.result
share/mysql-test/suite/funcs_1/r/memory_func_view.result
share/mysql-test/suite/funcs_1/r/memory_storedproc_02.result
share/mysql-test/suite/funcs_1/r/memory_storedproc_03.result
share/mysql-test/suite/funcs_1/r/memory_storedproc_06.result
share/mysql-test/suite/funcs_1/r/memory_storedproc_07.result
share/mysql-test/suite/funcs_1/r/memory_storedproc_08.result
share/mysql-test/suite/funcs_1/r/memory_storedproc_10.result
share/mysql-test/suite/funcs_1/r/memory_trig_0102.result
share/mysql-test/suite/funcs_1/r/memory_trig_03.result
share/mysql-test/suite/funcs_1/r/memory_trig_03e.result
share/mysql-test/suite/funcs_1/r/memory_trig_0407.result
share/mysql-test/suite/funcs_1/r/memory_trig_08.result
share/mysql-test/suite/funcs_1/r/memory_trig_09.result
share/mysql-test/suite/funcs_1/r/memory_trig_1011ext.result
share/mysql-test/suite/funcs_1/r/memory_views.result
share/mysql-test/suite/funcs_1/r/myisam_bitdata.result
share/mysql-test/suite/funcs_1/r/myisam_cursors.result
share/mysql-test/suite/funcs_1/r/myisam_func_view.result
share/mysql-test/suite/funcs_1/r/myisam_storedproc_02.result
share/mysql-test/suite/funcs_1/r/myisam_storedproc_03.result
share/mysql-test/suite/funcs_1/r/myisam_storedproc_06.result
share/mysql-test/suite/funcs_1/r/myisam_storedproc_07.result
share/mysql-test/suite/funcs_1/r/myisam_storedproc_08.result
share/mysql-test/suite/funcs_1/r/myisam_storedproc_10.result
share/mysql-test/suite/funcs_1/r/myisam_trig_0102.result
share/mysql-test/suite/funcs_1/r/myisam_trig_03.result
share/mysql-test/suite/funcs_1/r/myisam_trig_03e.result
share/mysql-test/suite/funcs_1/r/myisam_trig_0407.result
share/mysql-test/suite/funcs_1/r/myisam_trig_08.result
share/mysql-test/suite/funcs_1/r/myisam_trig_09.result
share/mysql-test/suite/funcs_1/r/myisam_trig_1011ext.result
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/funcs_1/r/myisam_views-big.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/funcs_1/r/ndb_bitdata.result
share/mysql-test/suite/funcs_1/r/ndb_cursors.result
share/mysql-test/suite/funcs_1/r/ndb_func_view.result
share/mysql-test/suite/funcs_1/r/ndb_storedproc_02.result
share/mysql-test/suite/funcs_1/r/ndb_storedproc_03.result
share/mysql-test/suite/funcs_1/r/ndb_storedproc_06.result
share/mysql-test/suite/funcs_1/r/ndb_storedproc_07.result
share/mysql-test/suite/funcs_1/r/ndb_storedproc_08.result
share/mysql-test/suite/funcs_1/r/ndb_storedproc_10.result
share/mysql-test/suite/funcs_1/r/ndb_trig_0102.result
share/mysql-test/suite/funcs_1/r/ndb_trig_03.result
share/mysql-test/suite/funcs_1/r/ndb_trig_03e.result
share/mysql-test/suite/funcs_1/r/ndb_trig_0407.result
share/mysql-test/suite/funcs_1/r/ndb_trig_08.result
share/mysql-test/suite/funcs_1/r/ndb_trig_09.result
share/mysql-test/suite/funcs_1/r/ndb_trig_1011ext.result
share/mysql-test/suite/funcs_1/r/ndb_views.result
share/mysql-test/suite/funcs_1/r/processlist_priv_no_prot.result
share/mysql-test/suite/funcs_1/r/processlist_priv_ps.result
share/mysql-test/suite/funcs_1/r/processlist_val_no_prot.result
share/mysql-test/suite/funcs_1/r/processlist_val_ps.result
share/mysql-test/suite/funcs_1/r/storedproc.result
share/mysql-test/suite/funcs_1/storedproc/cleanup_sp_tb.inc
share/mysql-test/suite/funcs_1/storedproc/load_sp_tb.inc
share/mysql-test/suite/funcs_1/storedproc/param_check.inc
share/mysql-test/suite/funcs_1/storedproc/storedproc_02.inc
share/mysql-test/suite/funcs_1/storedproc/storedproc_03.inc
share/mysql-test/suite/funcs_1/storedproc/storedproc_06.inc
share/mysql-test/suite/funcs_1/storedproc/storedproc_07.inc
share/mysql-test/suite/funcs_1/storedproc/storedproc_08.inc
share/mysql-test/suite/funcs_1/storedproc/storedproc_08_show.inc
share/mysql-test/suite/funcs_1/storedproc/storedproc_10.inc
share/mysql-test/suite/funcs_1/t/charset_collation.test
share/mysql-test/suite/funcs_1/t/disabled.def
share/mysql-test/suite/funcs_1/t/innodb_bitdata.test
share/mysql-test/suite/funcs_1/t/innodb_cursors.test
share/mysql-test/suite/funcs_1/t/innodb_func_view.test
share/mysql-test/suite/funcs_1/t/innodb_storedproc_02.test
share/mysql-test/suite/funcs_1/t/innodb_storedproc_03.test
share/mysql-test/suite/funcs_1/t/innodb_storedproc_06.test
share/mysql-test/suite/funcs_1/t/innodb_storedproc_07.test
share/mysql-test/suite/funcs_1/t/innodb_storedproc_08.test
share/mysql-test/suite/funcs_1/t/innodb_storedproc_10.test
share/mysql-test/suite/funcs_1/t/innodb_trig_0102.test
share/mysql-test/suite/funcs_1/t/innodb_trig_03.test
share/mysql-test/suite/funcs_1/t/innodb_trig_03e.test
share/mysql-test/suite/funcs_1/t/innodb_trig_0407.test
share/mysql-test/suite/funcs_1/t/innodb_trig_08.test
share/mysql-test/suite/funcs_1/t/innodb_trig_09.test
share/mysql-test/suite/funcs_1/t/innodb_trig_1011ext.test
share/mysql-test/suite/funcs_1/t/innodb_trig_frkey.test
share/mysql-test/suite/funcs_1/t/innodb_views.test
share/mysql-test/suite/funcs_1/t/is_basics_mixed.test
share/mysql-test/suite/funcs_1/t/is_character_sets.test
share/mysql-test/suite/funcs_1/t/is_cml_innodb.test
share/mysql-test/suite/funcs_1/t/is_cml_memory.test
share/mysql-test/suite/funcs_1/t/is_cml_myisam.test
share/mysql-test/suite/funcs_1/t/is_cml_ndb.test
share/mysql-test/suite/funcs_1/t/is_coll_char_set_appl.test
share/mysql-test/suite/funcs_1/t/is_collations.test
share/mysql-test/suite/funcs_1/t/is_column_privileges.test
share/mysql-test/suite/funcs_1/t/is_column_privileges_is_mysql_test.test
share/mysql-test/suite/funcs_1/t/is_columns.test
share/mysql-test/suite/funcs_1/t/is_columns_innodb.test
share/mysql-test/suite/funcs_1/t/is_columns_is.test
share/mysql-test/suite/funcs_1/t/is_columns_is_embedded.test
share/mysql-test/suite/funcs_1/t/is_columns_memory.test
share/mysql-test/suite/funcs_1/t/is_columns_myisam.test
share/mysql-test/suite/funcs_1/t/is_columns_myisam_embedded.test
share/mysql-test/suite/funcs_1/t/is_columns_mysql.test
share/mysql-test/suite/funcs_1/t/is_columns_mysql_embedded.test
share/mysql-test/suite/funcs_1/t/is_columns_ndb.test
share/mysql-test/suite/funcs_1/t/is_engines.test
share/mysql-test/suite/funcs_1/t/is_engines_archive.test
share/mysql-test/suite/funcs_1/t/is_engines_blackhole.test
share/mysql-test/suite/funcs_1/t/is_engines_csv.test
share/mysql-test/suite/funcs_1/t/is_engines_federated.test
share/mysql-test/suite/funcs_1/t/is_engines_innodb.test
share/mysql-test/suite/funcs_1/t/is_engines_memory.test
share/mysql-test/suite/funcs_1/t/is_engines_merge.test
share/mysql-test/suite/funcs_1/t/is_engines_myisam.test
share/mysql-test/suite/funcs_1/t/is_engines_ndb.test
share/mysql-test/suite/funcs_1/t/is_events.test
share/mysql-test/suite/funcs_1/t/is_key_column_usage.test
share/mysql-test/suite/funcs_1/t/is_key_column_usage_embedded.test
share/mysql-test/suite/funcs_1/t/is_routines.test
share/mysql-test/suite/funcs_1/t/is_routines_embedded.test
share/mysql-test/suite/funcs_1/t/is_schema_privileges.test
share/mysql-test/suite/funcs_1/t/is_schema_privileges_is_mysql_test.test
share/mysql-test/suite/funcs_1/t/is_schemata.test
share/mysql-test/suite/funcs_1/t/is_schemata_embedded.test
share/mysql-test/suite/funcs_1/t/is_schemata_is_mysql_test.test
share/mysql-test/suite/funcs_1/t/is_statistics.test
share/mysql-test/suite/funcs_1/t/is_statistics_is.test
share/mysql-test/suite/funcs_1/t/is_statistics_mysql.test
share/mysql-test/suite/funcs_1/t/is_statistics_mysql_embedded.test
share/mysql-test/suite/funcs_1/t/is_table_constraints.test
share/mysql-test/suite/funcs_1/t/is_table_constraints_is.test
share/mysql-test/suite/funcs_1/t/is_table_constraints_mysql.test
share/mysql-test/suite/funcs_1/t/is_table_constraints_mysql_embedded.test
share/mysql-test/suite/funcs_1/t/is_table_privileges.test
share/mysql-test/suite/funcs_1/t/is_tables.test
share/mysql-test/suite/funcs_1/t/is_tables_embedded.test
share/mysql-test/suite/funcs_1/t/is_tables_innodb.test
share/mysql-test/suite/funcs_1/t/is_tables_is.test
share/mysql-test/suite/funcs_1/t/is_tables_memory.test
share/mysql-test/suite/funcs_1/t/is_tables_myisam.test
share/mysql-test/suite/funcs_1/t/is_tables_myisam_embedded.test
share/mysql-test/suite/funcs_1/t/is_tables_mysql.test
share/mysql-test/suite/funcs_1/t/is_tables_mysql_embedded.test
share/mysql-test/suite/funcs_1/t/is_tables_ndb.test
share/mysql-test/suite/funcs_1/t/is_triggers.test
share/mysql-test/suite/funcs_1/t/is_triggers_embedded.test
share/mysql-test/suite/funcs_1/t/is_user_privileges.test
share/mysql-test/suite/funcs_1/t/is_views.test
share/mysql-test/suite/funcs_1/t/is_views_embedded.test
share/mysql-test/suite/funcs_1/t/memory_bitdata.test
share/mysql-test/suite/funcs_1/t/memory_cursors.test
share/mysql-test/suite/funcs_1/t/memory_func_view.test
share/mysql-test/suite/funcs_1/t/memory_storedproc_02.test
share/mysql-test/suite/funcs_1/t/memory_storedproc_03.test
share/mysql-test/suite/funcs_1/t/memory_storedproc_06.test
share/mysql-test/suite/funcs_1/t/memory_storedproc_07.test
share/mysql-test/suite/funcs_1/t/memory_storedproc_08.test
share/mysql-test/suite/funcs_1/t/memory_storedproc_10.test
share/mysql-test/suite/funcs_1/t/memory_trig_0102.test
share/mysql-test/suite/funcs_1/t/memory_trig_03.test
share/mysql-test/suite/funcs_1/t/memory_trig_03e.test
share/mysql-test/suite/funcs_1/t/memory_trig_0407.test
share/mysql-test/suite/funcs_1/t/memory_trig_08.test
share/mysql-test/suite/funcs_1/t/memory_trig_09.test
share/mysql-test/suite/funcs_1/t/memory_trig_1011ext.test
share/mysql-test/suite/funcs_1/t/memory_views.test
share/mysql-test/suite/funcs_1/t/myisam_bitdata.test
share/mysql-test/suite/funcs_1/t/myisam_cursors.test
share/mysql-test/suite/funcs_1/t/myisam_func_view.test
share/mysql-test/suite/funcs_1/t/myisam_storedproc_02.test
share/mysql-test/suite/funcs_1/t/myisam_storedproc_03.test
share/mysql-test/suite/funcs_1/t/myisam_storedproc_06.test
share/mysql-test/suite/funcs_1/t/myisam_storedproc_07.test
share/mysql-test/suite/funcs_1/t/myisam_storedproc_08.test
share/mysql-test/suite/funcs_1/t/myisam_storedproc_10.test
share/mysql-test/suite/funcs_1/t/myisam_trig_0102.test
share/mysql-test/suite/funcs_1/t/myisam_trig_03.test
share/mysql-test/suite/funcs_1/t/myisam_trig_03e.test
share/mysql-test/suite/funcs_1/t/myisam_trig_0407.test
share/mysql-test/suite/funcs_1/t/myisam_trig_08.test
share/mysql-test/suite/funcs_1/t/myisam_trig_09.test
share/mysql-test/suite/funcs_1/t/myisam_trig_1011ext.test
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/funcs_1/t/myisam_views-big.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/funcs_1/t/ndb_bitdata.test
share/mysql-test/suite/funcs_1/t/ndb_cursors.test
share/mysql-test/suite/funcs_1/t/ndb_func_view.test
share/mysql-test/suite/funcs_1/t/ndb_storedproc_02.test
share/mysql-test/suite/funcs_1/t/ndb_storedproc_03.test
share/mysql-test/suite/funcs_1/t/ndb_storedproc_06.test
share/mysql-test/suite/funcs_1/t/ndb_storedproc_07.test
share/mysql-test/suite/funcs_1/t/ndb_storedproc_08.test
share/mysql-test/suite/funcs_1/t/ndb_storedproc_10.test
share/mysql-test/suite/funcs_1/t/ndb_trig_0102.test
share/mysql-test/suite/funcs_1/t/ndb_trig_03.test
share/mysql-test/suite/funcs_1/t/ndb_trig_03e.test
share/mysql-test/suite/funcs_1/t/ndb_trig_0407.test
share/mysql-test/suite/funcs_1/t/ndb_trig_08.test
share/mysql-test/suite/funcs_1/t/ndb_trig_09.test
share/mysql-test/suite/funcs_1/t/ndb_trig_1011ext.test
share/mysql-test/suite/funcs_1/t/ndb_views.test
share/mysql-test/suite/funcs_1/t/processlist_priv_no_prot.test
share/mysql-test/suite/funcs_1/t/processlist_priv_ps.test
share/mysql-test/suite/funcs_1/t/processlist_val_no_prot.test
share/mysql-test/suite/funcs_1/t/processlist_val_ps.test
share/mysql-test/suite/funcs_1/t/storedproc.test
share/mysql-test/suite/funcs_1/t/suite.opt
share/mysql-test/suite/funcs_1/triggers/trig_frkey.inc
share/mysql-test/suite/funcs_1/triggers/trig_frkey2.inc
share/mysql-test/suite/funcs_1/triggers/triggers_0102.inc
share/mysql-test/suite/funcs_1/triggers/triggers_03.inc
share/mysql-test/suite/funcs_1/triggers/triggers_03e_columns.inc
share/mysql-test/suite/funcs_1/triggers/triggers_03e_db_level.inc
share/mysql-test/suite/funcs_1/triggers/triggers_03e_db_table_mix.inc
share/mysql-test/suite/funcs_1/triggers/triggers_03e_definer.inc
share/mysql-test/suite/funcs_1/triggers/triggers_03e_global_db_mix.inc
share/mysql-test/suite/funcs_1/triggers/triggers_03e_prepare.inc
share/mysql-test/suite/funcs_1/triggers/triggers_03e_table_level.inc
share/mysql-test/suite/funcs_1/triggers/triggers_03e_transaction.inc
share/mysql-test/suite/funcs_1/triggers/triggers_0407.inc
share/mysql-test/suite/funcs_1/triggers/triggers_08.inc
share/mysql-test/suite/funcs_1/triggers/triggers_09.inc
share/mysql-test/suite/funcs_1/triggers/triggers_1011ext.inc
share/mysql-test/suite/funcs_1/views/func_view.inc
share/mysql-test/suite/funcs_1/views/fv1.inc
share/mysql-test/suite/funcs_1/views/fv2.inc
share/mysql-test/suite/funcs_1/views/fv_cast.inc
share/mysql-test/suite/funcs_1/views/fv_if1.inc
share/mysql-test/suite/funcs_1/views/fv_if2.inc
share/mysql-test/suite/funcs_1/views/fv_ifnull.inc
share/mysql-test/suite/funcs_1/views/views_master.inc
share/mysql-test/suite/funcs_2/charset/charset_master.test
share/mysql-test/suite/funcs_2/data/charset_utf8.txt
share/mysql-test/suite/funcs_2/include/check_charset.inc
share/mysql-test/suite/funcs_2/include/check_charset_ucs2.inc
share/mysql-test/suite/funcs_2/include/check_charset_utf8.inc
share/mysql-test/suite/funcs_2/lib/gen_charset_utf8.pl
share/mysql-test/suite/funcs_2/r/innodb_charset.result
share/mysql-test/suite/funcs_2/r/memory_charset.result
share/mysql-test/suite/funcs_2/r/myisam_charset.result
share/mysql-test/suite/funcs_2/r/ndb_charset.result
share/mysql-test/suite/funcs_2/readme.txt
share/mysql-test/suite/funcs_2/t/disabled.def
share/mysql-test/suite/funcs_2/t/innodb_charset.test
share/mysql-test/suite/funcs_2/t/memory_charset.test
share/mysql-test/suite/funcs_2/t/myisam_charset.test
share/mysql-test/suite/funcs_2/t/ndb_charset.test
share/mysql-test/suite/funcs_2/t/suite.opt
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/r/innodb-autoinc-44030.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/r/innodb-autoinc-optimize.result
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/r/innodb-autoinc.result
share/mysql-test/suite/innodb/r/innodb-lock.result
share/mysql-test/suite/innodb/r/innodb-replace.result
share/mysql-test/suite/innodb/r/innodb-semi-consistent.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/r/innodb-ucs2.result
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/r/innodb.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/r/innodb_autoinc_lock_mode_zero.result
Changes 5.1.62: * New utf8_general_mysql500_ci and ucs2_general_mysql500_ci collations have been added that preserve the behavior of utf8_general_ci and ucs2_general_ci from versions of MySQL previous to 5.1.24. Bug 27877 corrected an error in the original collations but introduced an incompatibility for columns that contain German 'ß' LATIN SMALL LETTER SHARP S. (As a result of the fix, that character compares equal to characters with which it previously compared different.) A symptom of the problem after upgrading to MySQL 5.1.24 or newer from a version older than 5.1.24 is that CHECK TABLE produces this error: * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Bugs Fixed
2012-04-08 21:10:58 +02:00
share/mysql-test/suite/innodb/r/innodb_bug11754376.result
Update mysql51-{client,server} to 5.1.63 (MySQL 5.1.63). Changes (http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html): * Security Fix: Bug #64884 was fixed. * Security Fix: Bug #59387 was fixed. * InnoDB: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. (Bug #13847885) * InnoDB: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. (Bug #12861864, Bug #11766019) * InnoDB: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. (Bug #11766634, Bug #59783) * Partitioning: After updating a row of a partitioned table and selecting that row within the same transaction with the query cache enabled, then performing a ROLLBACK, the same result was returned by an identical SELECT issued in a new transaction. (Bug #11761296, Bug #53775) * Replication: The --relay-log-space-limit option was sometimes ignored. More specifically, when the SQL thread went to sleep, it allowed the I/O thread to queue additional events in such a way that the relay log space limit was bypassed, and the number of events in the queue could grow well past the point where the relay logs needed to be rotated. Now in such cases, the SQL thread checks to see whether the I/O thread should rotate and provide the SQL thread a chance to purge the logs (thus freeing space). Note that, when the SQL thread is in the middle of a transaction, it cannot purge the logs; it can only ask for more events until the transaction is complete. Once the transaction is finished, the SQL thread can immediately instruct the I/O thread to rotate. (Bug #12400313, Bug #64503) References: See also Bug #13806492. * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored procedures on slave servers could cause replication failures. (Bug #12601974) * If the system time was adjusted backward during query execution, the apparent execution time could be negative. But in some cases these queries would be written to the slow query log, with the negative execution time written as a large unsigned number. Now statements with apparent negative execution time are not written to the slow query log. (Bug #63524, Bug #13454045) References: See also Bug #27208. * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * SHOW statements treated stored procedure, stored function, and event names as case sensitive. (Bug #56224, Bug #11763507) * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 14:59:39 +02:00
share/mysql-test/suite/innodb/r/innodb_bug11766634.result
Changes 5.1.62: * New utf8_general_mysql500_ci and ucs2_general_mysql500_ci collations have been added that preserve the behavior of utf8_general_ci and ucs2_general_ci from versions of MySQL previous to 5.1.24. Bug 27877 corrected an error in the original collations but introduced an incompatibility for columns that contain German 'ß' LATIN SMALL LETTER SHARP S. (As a result of the fix, that character compares equal to characters with which it previously compared different.) A symptom of the problem after upgrading to MySQL 5.1.24 or newer from a version older than 5.1.24 is that CHECK TABLE produces this error: * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Bugs Fixed
2012-04-08 21:10:58 +02:00
share/mysql-test/suite/innodb/r/innodb_bug12400341.result
Changes 5.1.60: * Upgrading from an Advanced GPL RPM package to an Advanced RPM package did not work. Now on Linux it is possible to use rpm -U to replace any installed MySQL product by any other of the same release family. It is not necessary to remove the old produce with rpm -e first. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. Bugs Fixed * Important Change: InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Replication: Issuing the following statements, in the order shown, could cause a deadlock between the user thread and I/O thread. * more...
2011-12-02 15:25:09 +01:00
share/mysql-test/suite/innodb/r/innodb_bug12661768.result
Changes 5.1.62: * New utf8_general_mysql500_ci and ucs2_general_mysql500_ci collations have been added that preserve the behavior of utf8_general_ci and ucs2_general_ci from versions of MySQL previous to 5.1.24. Bug 27877 corrected an error in the original collations but introduced an incompatibility for columns that contain German 'ß' LATIN SMALL LETTER SHARP S. (As a result of the fix, that character compares equal to characters with which it previously compared different.) A symptom of the problem after upgrading to MySQL 5.1.24 or newer from a version older than 5.1.24 is that CHECK TABLE produces this error: * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Bugs Fixed
2012-04-08 21:10:58 +02:00
share/mysql-test/suite/innodb/r/innodb_bug13510739.result
Update mysql51-{client,server} to 5.1.63 (MySQL 5.1.63). Changes (http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html): * Security Fix: Bug #64884 was fixed. * Security Fix: Bug #59387 was fixed. * InnoDB: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. (Bug #13847885) * InnoDB: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. (Bug #12861864, Bug #11766019) * InnoDB: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. (Bug #11766634, Bug #59783) * Partitioning: After updating a row of a partitioned table and selecting that row within the same transaction with the query cache enabled, then performing a ROLLBACK, the same result was returned by an identical SELECT issued in a new transaction. (Bug #11761296, Bug #53775) * Replication: The --relay-log-space-limit option was sometimes ignored. More specifically, when the SQL thread went to sleep, it allowed the I/O thread to queue additional events in such a way that the relay log space limit was bypassed, and the number of events in the queue could grow well past the point where the relay logs needed to be rotated. Now in such cases, the SQL thread checks to see whether the I/O thread should rotate and provide the SQL thread a chance to purge the logs (thus freeing space). Note that, when the SQL thread is in the middle of a transaction, it cannot purge the logs; it can only ask for more events until the transaction is complete. Once the transaction is finished, the SQL thread can immediately instruct the I/O thread to rotate. (Bug #12400313, Bug #64503) References: See also Bug #13806492. * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored procedures on slave servers could cause replication failures. (Bug #12601974) * If the system time was adjusted backward during query execution, the apparent execution time could be negative. But in some cases these queries would be written to the slow query log, with the negative execution time written as a large unsigned number. Now statements with apparent negative execution time are not written to the slow query log. (Bug #63524, Bug #13454045) References: See also Bug #27208. * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * SHOW statements treated stored procedure, stored function, and event names as case sensitive. (Bug #56224, Bug #11763507) * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 14:59:39 +02:00
share/mysql-test/suite/innodb/r/innodb_bug13635833.result
Changes 5.1.71: Functionality Added or Changed * comp_err now checks to make sure that new errors are not being added to MySQL 5.1 or 5.5 because the set of errors for these series is frozen. Bugs Fixed * InnoDB: During an insert buffer merge, InnoDB would invoke lock_rec_restore_from_page_infimum() on a potentially invalid record pointer. * InnoDB: The page_zip_validate() consistency check would fail after compressing a page, in page_zip_compress(). This problem was caused by page_zip_decompress(), which would fail to set heap_no correctly when a record contained no user data bytes. A record with no user data bytes occurs when, for example, a primary key is an empty string and all secondary index fields are NULL or an empty string. * InnoDB: The pthread_mutex, commit_threads_m, which was initialized but never used, has been removed from the code base. * Partitioning: When dropping a partitioned table, the table's .par file was deleted first, before the table definition or data. This meant that, if the server failed during the drop operation, the table could be left in an inconsistent state in which it could neither be accessed nor dropped. * Shared-compatibility conflict errors occurred for RPM install operations, even if no shared-compatibility RPMs were already installed. * A user variable referenced during execution of a prepared statement is set to memory that is freed at the end of execution. A second execution of the statement could result in Valgrind warnings when accessing this memory. * Misoptimization of left expressions in prepared statements could cause a server exit. * Subsequent to Prepared statement needs to be re-prepared errors, inserts into DECIMAL columns caused a server exit. * Assigning the result of a subquery to a user variable raised an assertion when the outer query included DISTINCT and GROUP BY.
2013-08-04 12:20:24 +02:00
share/mysql-test/suite/innodb/r/innodb_bug14676111.result
Changes 5.1.67: Bug fixes http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-67.html
2013-01-21 09:58:43 +01:00
share/mysql-test/suite/innodb/r/innodb_bug14704286.result
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/r/innodb_bug21704.result
Update MySQL package to 5.1.56. Functionality added or changed: * mysqldump --xml now displays comments from column definitions. (Bug #13618) Bugs fixed: * InnoDB Storage Engine: InnoDB returned values for ¡Èrows examined¡É in the query plan that were higher than expected. NULL values were treated in an inconsistent way. The inaccurate statistics could trigger ¡Èfalse positives¡É in combination with the MAX_JOIN_SIZE setting, because the queries did not really examine as many rows as reported. (Bug #30423) * Partitioning: Trying to use the same column more than once in the partitioning key when partitioning a table by KEY caused mysqld to crash. Such duplication of key columns is now expressly disallowed, and fails with an appropriate error. (Bug #53354, Bug #57924) * Replication: When using the statement-based logging format, INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements affecting transactional tables that did not fail were not written to the binary log if they did not insert any rows. (With statement-based logging, all successful statements should be logged, whether they do or do not cause any rows to be changed.) (Bug #59338) * Replication: Formerly, STOP SLAVE stopped the slave I/O thread first and then stopped the slave SQL thread; thus, it was possible for the I/O thread to stop after replicating only part of a transaction which the SQL thread was executing, in wich case¡½if the transaction could not be rolled back safely¡½the SQL thread could hang. Now, STOP SLAVE stops the slave SQL thread first and then stops the I/O thread; this guarantees that the I/O thread can fetch any remaining events in the transaction that the SQL thread is executing, so that the SQL thread can finish the transaction if it cannot be rolled back safely. (Bug #58546) * A query of the following form returned an incorrect result, where the values for col_name in the result set were entirely replaced with NULL values: SELECT DISTINCT col_name ... ORDER BY col_name DESC; (Bug #59308, Bug #11766241) * DELETE or UPDATE statements could fail if they used DATE or DATETIME values with a year, month, or day part of zero. (Bug #59173) * The ESCAPE clause for the LIKE operator allows only expressions that evaluate to a constant at execution time, but aggregrate functions were not being rejected. (Bug #59149) * Memory leaks detected by Valgrind, some of which could cause incorrect query results, were corrected. (Bug #59110, Bug #11766075) mysqlslap failed to check for a NULL return from mysql_store_result() and crashed trying to process the result set. (Bug #59109) * In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could cause a server crash. (Bug #58371) * When mysqldadmin was run with the --sleep and --count options, it went into an infinite loop executing the specified command. (Bug #58221) * Some string manipulating SQL functions use a shared string object intended to contain an immutable empty string. This object was used by the SQL function SUBSTRING_INDEX() to return an empty string when one argument was of the wrong datatype. If the string object was then modified by the SQL function INSERT(), undefined behavior ensued. (Bug #58165, Bug #11765225) * Parsing nested regular expressions could lead to recursion resulting in a stack overflow crash. (Bug #58026, Bug #11765099) * The mysql client went into an infinite loop if the standard input was a directory. (Bug #57450) * The expression const1 BETWEEN const2 AND field was optimized incorrectly and produced incorrect results. (Bug #57030, Bug #11764215) * Some RPM installation scripts used a hardcoded value for the data directory, which could result in a failed installation for users who have a nonstandard data directory location. The same was true for other configuration values such as the PID file name. (Bug #56581, Bug #11763817) * On FreeBSD and OpenBSD, the server incorrectly checked the range of the system date, causing legal values to be rejected. (Bug #55755, Bug #11763089) * When using ExtractValue() or UpdateXML(), if the XML to be read contained an incomplete XML comment, MySQL read beyond the end of the XML string when processing, leading to a crash of the server. (Bug #44332)
2011-03-08 15:06:43 +01:00
share/mysql-test/suite/innodb/r/innodb_bug30423.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/r/innodb_bug30919.result
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/r/innodb_bug34053.result
share/mysql-test/suite/innodb/r/innodb_bug34300.result
share/mysql-test/suite/innodb/r/innodb_bug35220.result
share/mysql-test/suite/innodb/r/innodb_bug38231.result
share/mysql-test/suite/innodb/r/innodb_bug39438.result
share/mysql-test/suite/innodb/r/innodb_bug40565.result
share/mysql-test/suite/innodb/r/innodb_bug42101-nonzero.result
share/mysql-test/suite/innodb/r/innodb_bug42101.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/r/innodb_bug42419.result
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/r/innodb_bug44369.result
share/mysql-test/suite/innodb/r/innodb_bug45357.result
share/mysql-test/suite/innodb/r/innodb_bug46000.result
share/mysql-test/suite/innodb/r/innodb_bug47621.result
share/mysql-test/suite/innodb/r/innodb_bug47777.result
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/suite/innodb/r/innodb_bug48024.result
share/mysql-test/suite/innodb/r/innodb_bug49164.result
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/r/innodb_bug51920.result
share/mysql-test/suite/innodb/r/innodb_bug52663.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/r/innodb_bug53674.result
Update mysql51-{client,server} to 5.1.50. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-50.html for full changes . InnoDB Notes: InnoDB Plugin has been upgraded to version 1.0.11. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), generic Linux RPM packages, and any builds produced with the icc compiler. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: Important Change: Replication: The LOAD DATA INFILE statement is now considered unsafe for statement-based replication. When using statement-based logging mode, the statement now produces a warning; when using mixed-format logging, the statement is made using the row-based format. (Bug#34283) Partitioning: UPDATE and INSERT statements affecting partitioned tables performed poorly when using row-based replication. (Bug#52517) Partitioning: INSERT ON DUPLICATE KEY UPDATE statements performed poorly on tables having many partitions. This was because the handler function for reading a row from a specific index was not optimized in the partitioning handler. (Bug#52455) The server could crash on shutdown, if started with --innodb-use-system-malloc=0. (Bug#55581) GROUP BY operations used max_sort_length inconsistently. (Bug#55188) Building MySQL on Solaris 8 x86 failed when using Sun Studio due to gcc inline assembler code. (Bug#55061) In debug builds, an assertion could be raised when the server tried to send an OK packet to the client after having failed to detect errors during processing of the WHERE condition of an UPDATE statement. (Bug#54734) The database server could crash when renaming a table that had active transactions. (This issue only affected the database server when built for debugging.) (Bug#54453) The server could crash during the recovery phase of startup, if it previously crashed while inserting BLOB or other large columns that use off-page storage into an InnoDB table created with ROW_FORMAT=REDUNDANT or ROW_FORMAT=COMPACT. (Bug#54408) For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#54358) A client could supply data in chunks to a prepared statement parameter other than of type TEXT or BLOB using the mysql_stmt_send_long_data() C API function (or COM_STMT_SEND_LONG_DATA command). This led to a crash because other data types are not valid for long data. (Bug#54041) mysql_secure_installation did not properly identify local accounts and could incorrectly remove nonlocal root accounts. (Bug#54004) Transactions could be incorrectly committed during recovery, rather than rolled back, if the server crashed and was restarted after performing ALTER TABLE...ADD PRIMARY KEY on an InnoDB table, or some other operation that involves copying the entire table. (Bug#53756) Portability problems in SHOW STATUS could lead to incorrect results on some platforms. (Bug#53493) Builds of MySQL generated a large number of warnings. (Bug#53445) With lower_case_table_names set to a nonzero value, searches for table or database names in INFORMATION_SCHEMA tables could produce incorrect results. (Bug#53095) The ABI check for MySQL failed to compile with gcc 4.5. (Bug#52514) mysql_secure_installation sometimes failed to locate the mysql client. (Bug#52274) Reading a ucs2 data file with LOAD DATA INFILE was subject to three problems. 1) Incorrect parsing of the file as ucs2 data, resulting in incorrect length of the parsed string. This is fixed by truncating the invalid trailing bytes (incomplete multibyte characters) when reading from the file. 2) Reads from a proper ucs2 file did not recognize newline characters. This is fixed by first checking whether a byte is a newline (or any other special character) before reading it as a part of a multibyte character. 3) When using user variables to hold column data, the character set of the user variable was set incorrectly to the database charset. This is fixed by setting it to the character set specified in the LOAD DATA INFILE statement, if any. (Bug#51876) Searches in INFORMATION_SCHEMA tables for rows matching a nonexistent database produced an error instead of an empty query result. (Bug#49542) On FreeBSD, memory mapping for MERGE tables could fail if underlying tables were empty. (Bug#47139) The my_like_range_xxx() functions returned badly formed maximum strings for Asian character sets, which caused problems for storage engines. (Bug#45012) A debugging assertion could be raised after a write failure to a closed socket. (Bug#42496) An assertion failure occurred within yaSSL for very long keys. (Bug#29784) See also Bug#53463.
2010-09-08 18:24:57 +02:00
share/mysql-test/suite/innodb/r/innodb_bug53756.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/r/innodb_bug54044.result
Update mysql51-{client,server} to 5.1.53. Most changes are related to replication and seems to no security fix. For more detail, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html
2010-11-26 14:52:58 +01:00
share/mysql-test/suite/innodb/r/innodb_bug56143.result
share/mysql-test/suite/innodb/r/innodb_bug56680.result
Update mysql51-{client,server} package from 5.1.51 to 5.1.52. This is maintainous release and pleare refer in detail: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html One note from the changes: * Security Fix: In prepared-statement mode, EXPLAIN for a SELECT from a derived table caused a server crash. (Bug#54488)
2010-11-04 16:57:07 +01:00
share/mysql-test/suite/innodb/r/innodb_bug56716.result
Update mysql51-{client,server} to 5.1.53. Most changes are related to replication and seems to no security fix. For more detail, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html
2010-11-26 14:52:58 +01:00
share/mysql-test/suite/innodb/r/innodb_bug57252.result
Update mysql51-{client,server} package from 5.1.51 to 5.1.52. This is maintainous release and pleare refer in detail: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html One note from the changes: * Security Fix: In prepared-statement mode, EXPLAIN for a SELECT from a derived table caused a server crash. (Bug#54488)
2010-11-04 16:57:07 +01:00
share/mysql-test/suite/innodb/r/innodb_bug57255.result
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/suite/innodb/r/innodb_bug59410.result
share/mysql-test/suite/innodb/r/innodb_bug59641.result
Update mysql51-{client,server} package to 5.1.57. This is simply maintenance release, no security fix. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-57.html in detail.
2011-05-08 18:01:57 +02:00
share/mysql-test/suite/innodb/r/innodb_bug60049.result
Update mysql51 to 5.1.65. While here, let to use OpenSSL instead of internal yaSSL with ssl option, may related to PR 46912. Changes in MySQL 5.1.65 (2012-08-09) Functionality Added or Changed * Important Change: The YEAR(2) data type is now deprecated because it is problematic. Support for YEAR(2) will be removed in a future release of MySQL. For more information, see Section 11.3.4, "YEAR(2) Limitations and Migrating to YEAR(4)". Bugs Fixed * The server did not build with gcc 4.7. (Bug #14238406) Changes in MySQL 5.1.64 (Not released) Functionality Added or Changed * Important Change: Replication: The SHOW BINARY LOGS statement (and its equivalent SHOW MASTER LOGS) may now be executed by a user with the REPLICATION CLIENT privilege. (Formerly, the SUPER privilege was necessary to use either form of this statement.)
2012-09-15 16:48:57 +02:00
share/mysql-test/suite/innodb/r/innodb_bug14007649.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/r/innodb_gis.result
share/mysql-test/suite/innodb/r/innodb_lock_wait_timeout_1.result
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/r/innodb_misc1.result
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/suite/innodb/r/innodb_multi_update.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/r/innodb_mysql.result
share/mysql-test/suite/innodb/r/innodb_mysql_rbk.result
share/mysql-test/suite/innodb/r/innodb_notembedded.result
Changes 5.1.61: * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. * An incorrect InnoDB assertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source file btr0pcur.ic and the variable cursor->pos_state. * The handle_segfault() signal-handler code in mysqld could itself crash due to calling unsafe functions. * ARCHIVE tables with NULL columns could cause server crashes or become corrupt under concurrent load. * Enabling myisam_use_mmap could cause the server to crash. * Concurrent access to ARCHIVE tables could cause corruption.
2012-01-12 18:41:21 +01:00
share/mysql-test/suite/innodb/r/innodb_replace.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/r/innodb_timeout_rollback.result
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/r/innodb_trx_weight.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/innodb/t/disabled.def
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/t/innodb-autoinc-44030.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/t/innodb-autoinc-optimize.test
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/t/innodb-autoinc.test
share/mysql-test/suite/innodb/t/innodb-lock.test
share/mysql-test/suite/innodb/t/innodb-master.opt
share/mysql-test/suite/innodb/t/innodb-replace.test
share/mysql-test/suite/innodb/t/innodb-semi-consistent-master.opt
share/mysql-test/suite/innodb/t/innodb-semi-consistent.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/t/innodb-ucs2.test
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/t/innodb.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/t/innodb_autoinc_lock_mode_zero-master.opt
share/mysql-test/suite/innodb/t/innodb_autoinc_lock_mode_zero.test
Changes 5.1.62: * New utf8_general_mysql500_ci and ucs2_general_mysql500_ci collations have been added that preserve the behavior of utf8_general_ci and ucs2_general_ci from versions of MySQL previous to 5.1.24. Bug 27877 corrected an error in the original collations but introduced an incompatibility for columns that contain German 'ß' LATIN SMALL LETTER SHARP S. (As a result of the fix, that character compares equal to characters with which it previously compared different.) A symptom of the problem after upgrading to MySQL 5.1.24 or newer from a version older than 5.1.24 is that CHECK TABLE produces this error: * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Bugs Fixed
2012-04-08 21:10:58 +02:00
share/mysql-test/suite/innodb/t/innodb_bug11754376.test
Update mysql51-{client,server} to 5.1.63 (MySQL 5.1.63). Changes (http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html): * Security Fix: Bug #64884 was fixed. * Security Fix: Bug #59387 was fixed. * InnoDB: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. (Bug #13847885) * InnoDB: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. (Bug #12861864, Bug #11766019) * InnoDB: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. (Bug #11766634, Bug #59783) * Partitioning: After updating a row of a partitioned table and selecting that row within the same transaction with the query cache enabled, then performing a ROLLBACK, the same result was returned by an identical SELECT issued in a new transaction. (Bug #11761296, Bug #53775) * Replication: The --relay-log-space-limit option was sometimes ignored. More specifically, when the SQL thread went to sleep, it allowed the I/O thread to queue additional events in such a way that the relay log space limit was bypassed, and the number of events in the queue could grow well past the point where the relay logs needed to be rotated. Now in such cases, the SQL thread checks to see whether the I/O thread should rotate and provide the SQL thread a chance to purge the logs (thus freeing space). Note that, when the SQL thread is in the middle of a transaction, it cannot purge the logs; it can only ask for more events until the transaction is complete. Once the transaction is finished, the SQL thread can immediately instruct the I/O thread to rotate. (Bug #12400313, Bug #64503) References: See also Bug #13806492. * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored procedures on slave servers could cause replication failures. (Bug #12601974) * If the system time was adjusted backward during query execution, the apparent execution time could be negative. But in some cases these queries would be written to the slow query log, with the negative execution time written as a large unsigned number. Now statements with apparent negative execution time are not written to the slow query log. (Bug #63524, Bug #13454045) References: See also Bug #27208. * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * SHOW statements treated stored procedure, stored function, and event names as case sensitive. (Bug #56224, Bug #11763507) * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 14:59:39 +02:00
share/mysql-test/suite/innodb/t/innodb_bug11766634.test
Changes 5.1.62: * New utf8_general_mysql500_ci and ucs2_general_mysql500_ci collations have been added that preserve the behavior of utf8_general_ci and ucs2_general_ci from versions of MySQL previous to 5.1.24. Bug 27877 corrected an error in the original collations but introduced an incompatibility for columns that contain German 'ß' LATIN SMALL LETTER SHARP S. (As a result of the fix, that character compares equal to characters with which it previously compared different.) A symptom of the problem after upgrading to MySQL 5.1.24 or newer from a version older than 5.1.24 is that CHECK TABLE produces this error: * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Bugs Fixed
2012-04-08 21:10:58 +02:00
share/mysql-test/suite/innodb/t/innodb_bug12400341-master.opt
share/mysql-test/suite/innodb/t/innodb_bug12400341.test
Changes 5.1.60: * Upgrading from an Advanced GPL RPM package to an Advanced RPM package did not work. Now on Linux it is possible to use rpm -U to replace any installed MySQL product by any other of the same release family. It is not necessary to remove the old produce with rpm -e first. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. Bugs Fixed * Important Change: InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Replication: Issuing the following statements, in the order shown, could cause a deadlock between the user thread and I/O thread. * more...
2011-12-02 15:25:09 +01:00
share/mysql-test/suite/innodb/t/innodb_bug12661768.test
Changes 5.1.62: * New utf8_general_mysql500_ci and ucs2_general_mysql500_ci collations have been added that preserve the behavior of utf8_general_ci and ucs2_general_ci from versions of MySQL previous to 5.1.24. Bug 27877 corrected an error in the original collations but introduced an incompatibility for columns that contain German 'ß' LATIN SMALL LETTER SHARP S. (As a result of the fix, that character compares equal to characters with which it previously compared different.) A symptom of the problem after upgrading to MySQL 5.1.24 or newer from a version older than 5.1.24 is that CHECK TABLE produces this error: * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Bugs Fixed
2012-04-08 21:10:58 +02:00
share/mysql-test/suite/innodb/t/innodb_bug13510739.test
Update mysql51-{client,server} to 5.1.63 (MySQL 5.1.63). Changes (http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html): * Security Fix: Bug #64884 was fixed. * Security Fix: Bug #59387 was fixed. * InnoDB: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. (Bug #13847885) * InnoDB: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. (Bug #12861864, Bug #11766019) * InnoDB: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. (Bug #11766634, Bug #59783) * Partitioning: After updating a row of a partitioned table and selecting that row within the same transaction with the query cache enabled, then performing a ROLLBACK, the same result was returned by an identical SELECT issued in a new transaction. (Bug #11761296, Bug #53775) * Replication: The --relay-log-space-limit option was sometimes ignored. More specifically, when the SQL thread went to sleep, it allowed the I/O thread to queue additional events in such a way that the relay log space limit was bypassed, and the number of events in the queue could grow well past the point where the relay logs needed to be rotated. Now in such cases, the SQL thread checks to see whether the I/O thread should rotate and provide the SQL thread a chance to purge the logs (thus freeing space). Note that, when the SQL thread is in the middle of a transaction, it cannot purge the logs; it can only ask for more events until the transaction is complete. Once the transaction is finished, the SQL thread can immediately instruct the I/O thread to rotate. (Bug #12400313, Bug #64503) References: See also Bug #13806492. * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored procedures on slave servers could cause replication failures. (Bug #12601974) * If the system time was adjusted backward during query execution, the apparent execution time could be negative. But in some cases these queries would be written to the slow query log, with the negative execution time written as a large unsigned number. Now statements with apparent negative execution time are not written to the slow query log. (Bug #63524, Bug #13454045) References: See also Bug #27208. * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * SHOW statements treated stored procedure, stored function, and event names as case sensitive. (Bug #56224, Bug #11763507) * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 14:59:39 +02:00
share/mysql-test/suite/innodb/t/innodb_bug13635833.test
Update mysql51 to 5.1.65. While here, let to use OpenSSL instead of internal yaSSL with ssl option, may related to PR 46912. Changes in MySQL 5.1.65 (2012-08-09) Functionality Added or Changed * Important Change: The YEAR(2) data type is now deprecated because it is problematic. Support for YEAR(2) will be removed in a future release of MySQL. For more information, see Section 11.3.4, "YEAR(2) Limitations and Migrating to YEAR(4)". Bugs Fixed * The server did not build with gcc 4.7. (Bug #14238406) Changes in MySQL 5.1.64 (Not released) Functionality Added or Changed * Important Change: Replication: The SHOW BINARY LOGS statement (and its equivalent SHOW MASTER LOGS) may now be executed by a user with the REPLICATION CLIENT privilege. (Formerly, the SUPER privilege was necessary to use either form of this statement.)
2012-09-15 16:48:57 +02:00
share/mysql-test/suite/innodb/t/innodb_bug14007649.test
Changes 5.1.71: Functionality Added or Changed * comp_err now checks to make sure that new errors are not being added to MySQL 5.1 or 5.5 because the set of errors for these series is frozen. Bugs Fixed * InnoDB: During an insert buffer merge, InnoDB would invoke lock_rec_restore_from_page_infimum() on a potentially invalid record pointer. * InnoDB: The page_zip_validate() consistency check would fail after compressing a page, in page_zip_compress(). This problem was caused by page_zip_decompress(), which would fail to set heap_no correctly when a record contained no user data bytes. A record with no user data bytes occurs when, for example, a primary key is an empty string and all secondary index fields are NULL or an empty string. * InnoDB: The pthread_mutex, commit_threads_m, which was initialized but never used, has been removed from the code base. * Partitioning: When dropping a partitioned table, the table's .par file was deleted first, before the table definition or data. This meant that, if the server failed during the drop operation, the table could be left in an inconsistent state in which it could neither be accessed nor dropped. * Shared-compatibility conflict errors occurred for RPM install operations, even if no shared-compatibility RPMs were already installed. * A user variable referenced during execution of a prepared statement is set to memory that is freed at the end of execution. A second execution of the statement could result in Valgrind warnings when accessing this memory. * Misoptimization of left expressions in prepared statements could cause a server exit. * Subsequent to Prepared statement needs to be re-prepared errors, inserts into DECIMAL columns caused a server exit. * Assigning the result of a subquery to a user variable raised an assertion when the outer query included DISTINCT and GROUP BY.
2013-08-04 12:20:24 +02:00
share/mysql-test/suite/innodb/t/innodb_bug14676111.test
Changes 5.1.67: Bug fixes http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-67.html
2013-01-21 09:58:43 +01:00
share/mysql-test/suite/innodb/t/innodb_bug14704286.test
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/t/innodb_bug21704.test
Update MySQL package to 5.1.56. Functionality added or changed: * mysqldump --xml now displays comments from column definitions. (Bug #13618) Bugs fixed: * InnoDB Storage Engine: InnoDB returned values for ¡Èrows examined¡É in the query plan that were higher than expected. NULL values were treated in an inconsistent way. The inaccurate statistics could trigger ¡Èfalse positives¡É in combination with the MAX_JOIN_SIZE setting, because the queries did not really examine as many rows as reported. (Bug #30423) * Partitioning: Trying to use the same column more than once in the partitioning key when partitioning a table by KEY caused mysqld to crash. Such duplication of key columns is now expressly disallowed, and fails with an appropriate error. (Bug #53354, Bug #57924) * Replication: When using the statement-based logging format, INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements affecting transactional tables that did not fail were not written to the binary log if they did not insert any rows. (With statement-based logging, all successful statements should be logged, whether they do or do not cause any rows to be changed.) (Bug #59338) * Replication: Formerly, STOP SLAVE stopped the slave I/O thread first and then stopped the slave SQL thread; thus, it was possible for the I/O thread to stop after replicating only part of a transaction which the SQL thread was executing, in wich case¡½if the transaction could not be rolled back safely¡½the SQL thread could hang. Now, STOP SLAVE stops the slave SQL thread first and then stops the I/O thread; this guarantees that the I/O thread can fetch any remaining events in the transaction that the SQL thread is executing, so that the SQL thread can finish the transaction if it cannot be rolled back safely. (Bug #58546) * A query of the following form returned an incorrect result, where the values for col_name in the result set were entirely replaced with NULL values: SELECT DISTINCT col_name ... ORDER BY col_name DESC; (Bug #59308, Bug #11766241) * DELETE or UPDATE statements could fail if they used DATE or DATETIME values with a year, month, or day part of zero. (Bug #59173) * The ESCAPE clause for the LIKE operator allows only expressions that evaluate to a constant at execution time, but aggregrate functions were not being rejected. (Bug #59149) * Memory leaks detected by Valgrind, some of which could cause incorrect query results, were corrected. (Bug #59110, Bug #11766075) mysqlslap failed to check for a NULL return from mysql_store_result() and crashed trying to process the result set. (Bug #59109) * In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could cause a server crash. (Bug #58371) * When mysqldadmin was run with the --sleep and --count options, it went into an infinite loop executing the specified command. (Bug #58221) * Some string manipulating SQL functions use a shared string object intended to contain an immutable empty string. This object was used by the SQL function SUBSTRING_INDEX() to return an empty string when one argument was of the wrong datatype. If the string object was then modified by the SQL function INSERT(), undefined behavior ensued. (Bug #58165, Bug #11765225) * Parsing nested regular expressions could lead to recursion resulting in a stack overflow crash. (Bug #58026, Bug #11765099) * The mysql client went into an infinite loop if the standard input was a directory. (Bug #57450) * The expression const1 BETWEEN const2 AND field was optimized incorrectly and produced incorrect results. (Bug #57030, Bug #11764215) * Some RPM installation scripts used a hardcoded value for the data directory, which could result in a failed installation for users who have a nonstandard data directory location. The same was true for other configuration values such as the PID file name. (Bug #56581, Bug #11763817) * On FreeBSD and OpenBSD, the server incorrectly checked the range of the system date, causing legal values to be rejected. (Bug #55755, Bug #11763089) * When using ExtractValue() or UpdateXML(), if the XML to be read contained an incomplete XML comment, MySQL read beyond the end of the XML string when processing, leading to a crash of the server. (Bug #44332)
2011-03-08 15:06:43 +01:00
share/mysql-test/suite/innodb/t/innodb_bug30423.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/t/innodb_bug30919-master.opt
share/mysql-test/suite/innodb/t/innodb_bug30919.test
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/t/innodb_bug34053.test
share/mysql-test/suite/innodb/t/innodb_bug34300.test
share/mysql-test/suite/innodb/t/innodb_bug35220.test
share/mysql-test/suite/innodb/t/innodb_bug38231.test
share/mysql-test/suite/innodb/t/innodb_bug39438-master.opt
share/mysql-test/suite/innodb/t/innodb_bug39438.test
share/mysql-test/suite/innodb/t/innodb_bug40565.test
share/mysql-test/suite/innodb/t/innodb_bug42101-nonzero-master.opt
share/mysql-test/suite/innodb/t/innodb_bug42101-nonzero.test
share/mysql-test/suite/innodb/t/innodb_bug42101.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/t/innodb_bug42419.test
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/t/innodb_bug44369.test
share/mysql-test/suite/innodb/t/innodb_bug45357.test
share/mysql-test/suite/innodb/t/innodb_bug46000.test
share/mysql-test/suite/innodb/t/innodb_bug47621.test
share/mysql-test/suite/innodb/t/innodb_bug47777.test
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/suite/innodb/t/innodb_bug48024.test
share/mysql-test/suite/innodb/t/innodb_bug49164.test
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/t/innodb_bug51920.test
share/mysql-test/suite/innodb/t/innodb_bug52663-master.opt
share/mysql-test/suite/innodb/t/innodb_bug52663.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/t/innodb_bug53674-master.opt
share/mysql-test/suite/innodb/t/innodb_bug53674.test
Update mysql51-{client,server} to 5.1.50. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-50.html for full changes . InnoDB Notes: InnoDB Plugin has been upgraded to version 1.0.11. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), generic Linux RPM packages, and any builds produced with the icc compiler. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: Important Change: Replication: The LOAD DATA INFILE statement is now considered unsafe for statement-based replication. When using statement-based logging mode, the statement now produces a warning; when using mixed-format logging, the statement is made using the row-based format. (Bug#34283) Partitioning: UPDATE and INSERT statements affecting partitioned tables performed poorly when using row-based replication. (Bug#52517) Partitioning: INSERT ON DUPLICATE KEY UPDATE statements performed poorly on tables having many partitions. This was because the handler function for reading a row from a specific index was not optimized in the partitioning handler. (Bug#52455) The server could crash on shutdown, if started with --innodb-use-system-malloc=0. (Bug#55581) GROUP BY operations used max_sort_length inconsistently. (Bug#55188) Building MySQL on Solaris 8 x86 failed when using Sun Studio due to gcc inline assembler code. (Bug#55061) In debug builds, an assertion could be raised when the server tried to send an OK packet to the client after having failed to detect errors during processing of the WHERE condition of an UPDATE statement. (Bug#54734) The database server could crash when renaming a table that had active transactions. (This issue only affected the database server when built for debugging.) (Bug#54453) The server could crash during the recovery phase of startup, if it previously crashed while inserting BLOB or other large columns that use off-page storage into an InnoDB table created with ROW_FORMAT=REDUNDANT or ROW_FORMAT=COMPACT. (Bug#54408) For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#54358) A client could supply data in chunks to a prepared statement parameter other than of type TEXT or BLOB using the mysql_stmt_send_long_data() C API function (or COM_STMT_SEND_LONG_DATA command). This led to a crash because other data types are not valid for long data. (Bug#54041) mysql_secure_installation did not properly identify local accounts and could incorrectly remove nonlocal root accounts. (Bug#54004) Transactions could be incorrectly committed during recovery, rather than rolled back, if the server crashed and was restarted after performing ALTER TABLE...ADD PRIMARY KEY on an InnoDB table, or some other operation that involves copying the entire table. (Bug#53756) Portability problems in SHOW STATUS could lead to incorrect results on some platforms. (Bug#53493) Builds of MySQL generated a large number of warnings. (Bug#53445) With lower_case_table_names set to a nonzero value, searches for table or database names in INFORMATION_SCHEMA tables could produce incorrect results. (Bug#53095) The ABI check for MySQL failed to compile with gcc 4.5. (Bug#52514) mysql_secure_installation sometimes failed to locate the mysql client. (Bug#52274) Reading a ucs2 data file with LOAD DATA INFILE was subject to three problems. 1) Incorrect parsing of the file as ucs2 data, resulting in incorrect length of the parsed string. This is fixed by truncating the invalid trailing bytes (incomplete multibyte characters) when reading from the file. 2) Reads from a proper ucs2 file did not recognize newline characters. This is fixed by first checking whether a byte is a newline (or any other special character) before reading it as a part of a multibyte character. 3) When using user variables to hold column data, the character set of the user variable was set incorrectly to the database charset. This is fixed by setting it to the character set specified in the LOAD DATA INFILE statement, if any. (Bug#51876) Searches in INFORMATION_SCHEMA tables for rows matching a nonexistent database produced an error instead of an empty query result. (Bug#49542) On FreeBSD, memory mapping for MERGE tables could fail if underlying tables were empty. (Bug#47139) The my_like_range_xxx() functions returned badly formed maximum strings for Asian character sets, which caused problems for storage engines. (Bug#45012) A debugging assertion could be raised after a write failure to a closed socket. (Bug#42496) An assertion failure occurred within yaSSL for very long keys. (Bug#29784) See also Bug#53463.
2010-09-08 18:24:57 +02:00
share/mysql-test/suite/innodb/t/innodb_bug53756-master.opt
share/mysql-test/suite/innodb/t/innodb_bug53756.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/t/innodb_bug54044.test
Update mysql51-{client,server} to 5.1.53. Most changes are related to replication and seems to no security fix. For more detail, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html
2010-11-26 14:52:58 +01:00
share/mysql-test/suite/innodb/t/innodb_bug56143.test
share/mysql-test/suite/innodb/t/innodb_bug56680.test
Update mysql51-{client,server} package from 5.1.51 to 5.1.52. This is maintainous release and pleare refer in detail: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html One note from the changes: * Security Fix: In prepared-statement mode, EXPLAIN for a SELECT from a derived table caused a server crash. (Bug#54488)
2010-11-04 16:57:07 +01:00
share/mysql-test/suite/innodb/t/innodb_bug56716.test
Update mysql51-{client,server} to 5.1.53. Most changes are related to replication and seems to no security fix. For more detail, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html
2010-11-26 14:52:58 +01:00
share/mysql-test/suite/innodb/t/innodb_bug57252.test
Update mysql51-{client,server} package from 5.1.51 to 5.1.52. This is maintainous release and pleare refer in detail: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html One note from the changes: * Security Fix: In prepared-statement mode, EXPLAIN for a SELECT from a derived table caused a server crash. (Bug#54488)
2010-11-04 16:57:07 +01:00
share/mysql-test/suite/innodb/t/innodb_bug57255.test
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/suite/innodb/t/innodb_bug59410.test
share/mysql-test/suite/innodb/t/innodb_bug59641.test
Update mysql51-{client,server} package to 5.1.57. This is simply maintenance release, no security fix. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-57.html in detail.
2011-05-08 18:01:57 +02:00
share/mysql-test/suite/innodb/t/innodb_bug60049-master.opt
share/mysql-test/suite/innodb/t/innodb_bug60049.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/t/innodb_gis.test
share/mysql-test/suite/innodb/t/innodb_lock_wait_timeout_1-master.opt
share/mysql-test/suite/innodb/t/innodb_lock_wait_timeout_1.test
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/t/innodb_misc1-master.opt
share/mysql-test/suite/innodb/t/innodb_misc1.test
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/suite/innodb/t/innodb_multi_update.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/t/innodb_mysql-master.opt
share/mysql-test/suite/innodb/t/innodb_mysql.test
share/mysql-test/suite/innodb/t/innodb_mysql_rbk-master.opt
share/mysql-test/suite/innodb/t/innodb_mysql_rbk.test
share/mysql-test/suite/innodb/t/innodb_notembedded.test
Changes 5.1.61: * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. * An incorrect InnoDB assertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source file btr0pcur.ic and the variable cursor->pos_state. * The handle_segfault() signal-handler code in mysqld could itself crash due to calling unsafe functions. * ARCHIVE tables with NULL columns could cause server crashes or become corrupt under concurrent load. * Enabling myisam_use_mmap could cause the server to crash. * Concurrent access to ARCHIVE tables could cause corruption.
2012-01-12 18:41:21 +01:00
share/mysql-test/suite/innodb/t/innodb_replace.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb/t/innodb_timeout_rollback-master.opt
share/mysql-test/suite/innodb/t/innodb_timeout_rollback.test
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/suite/innodb/t/innodb_trx_weight.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/include/ctype_innodb_like.inc
share/mysql-test/suite/innodb_plugin/include/innodb-index.inc
share/mysql-test/suite/innodb_plugin/include/innodb_trx_weight.inc
share/mysql-test/suite/innodb_plugin/r/innodb-analyze.result
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/innodb_plugin/r/innodb-autoinc-18274.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb-autoinc-44030.result
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/innodb_plugin/r/innodb-autoinc-56228.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb-autoinc-optimize.result
share/mysql-test/suite/innodb_plugin/r/innodb-autoinc.result
Changes 5.1.62: * New utf8_general_mysql500_ci and ucs2_general_mysql500_ci collations have been added that preserve the behavior of utf8_general_ci and ucs2_general_ci from versions of MySQL previous to 5.1.24. Bug 27877 corrected an error in the original collations but introduced an incompatibility for columns that contain German 'ß' LATIN SMALL LETTER SHARP S. (As a result of the fix, that character compares equal to characters with which it previously compared different.) A symptom of the problem after upgrading to MySQL 5.1.24 or newer from a version older than 5.1.24 is that CHECK TABLE produces this error: * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Bugs Fixed
2012-04-08 21:10:58 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb-blob.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb-consistent.result
Update mysql51-{client,server} package to 5.1.54. Functionality added or changed: * Support for the IBMDB2I storage engine has been removed. (Bug#58079) * The pstack library was nonfunctional and has been removed, along with the --with-pstack option for configure. The --enable-pstack option for mysqld is deprecated and will be removed in MySQL 5.5. (Bug#57210) Bugs fixed: * Performance: InnoDB Storage Engine: Improved concurrency when several ANALYZE TABLE or SHOW TABLE STATUS statements are run simultaneously for InnoDB tables. (Bug#53046) * InnoDB Storage Engine: For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#57799) * Partitioning: An INSERT ... ON DUPLICATE KEY UPDATE column = 0 statement on an AUTO_INCREMENT column caused the debug server to crash. (Bug#57890) * Several compilation problems were fixed. (Bug#57992, Bug#57993, Bug#57994, Bug#57995, Bug#57996, Bug#57997, Bug#58057) * Passing a string that was not null-terminated to UpdateXML() or ExtractValue() caused the server to fail with an assertion. (Bug#57279) * Queries executed using the Index Merge access method and a temporary file could return incorrect results. (Bug#56862) * The find_files() function used by SHOW statements performed redundant and unnecessary memory allocation. (Bug#51208)
2010-12-16 04:42:49 +01:00
share/mysql-test/suite/innodb_plugin/r/innodb-create-options.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb-index.result
share/mysql-test/suite/innodb_plugin/r/innodb-index_ucs2.result
share/mysql-test/suite/innodb_plugin/r/innodb-lock.result
share/mysql-test/suite/innodb_plugin/r/innodb-replace.result
share/mysql-test/suite/innodb_plugin/r/innodb-semi-consistent.result
share/mysql-test/suite/innodb_plugin/r/innodb-timeout.result
share/mysql-test/suite/innodb_plugin/r/innodb-ucs2.result
share/mysql-test/suite/innodb_plugin/r/innodb-use-sys-malloc.result
share/mysql-test/suite/innodb_plugin/r/innodb-zip.result
share/mysql-test/suite/innodb_plugin/r/innodb.result
share/mysql-test/suite/innodb_plugin/r/innodb_autoinc_lock_mode_zero.result
Changes 5.1.62: * New utf8_general_mysql500_ci and ucs2_general_mysql500_ci collations have been added that preserve the behavior of utf8_general_ci and ucs2_general_ci from versions of MySQL previous to 5.1.24. Bug 27877 corrected an error in the original collations but introduced an incompatibility for columns that contain German 'ß' LATIN SMALL LETTER SHARP S. (As a result of the fix, that character compares equal to characters with which it previously compared different.) A symptom of the problem after upgrading to MySQL 5.1.24 or newer from a version older than 5.1.24 is that CHECK TABLE produces this error: * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Bugs Fixed
2012-04-08 21:10:58 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug11754376.result
Update mysql51-{client,server} to 5.1.63 (MySQL 5.1.63). Changes (http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html): * Security Fix: Bug #64884 was fixed. * Security Fix: Bug #59387 was fixed. * InnoDB: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. (Bug #13847885) * InnoDB: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. (Bug #12861864, Bug #11766019) * InnoDB: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. (Bug #11766634, Bug #59783) * Partitioning: After updating a row of a partitioned table and selecting that row within the same transaction with the query cache enabled, then performing a ROLLBACK, the same result was returned by an identical SELECT issued in a new transaction. (Bug #11761296, Bug #53775) * Replication: The --relay-log-space-limit option was sometimes ignored. More specifically, when the SQL thread went to sleep, it allowed the I/O thread to queue additional events in such a way that the relay log space limit was bypassed, and the number of events in the queue could grow well past the point where the relay logs needed to be rotated. Now in such cases, the SQL thread checks to see whether the I/O thread should rotate and provide the SQL thread a chance to purge the logs (thus freeing space). Note that, when the SQL thread is in the middle of a transaction, it cannot purge the logs; it can only ask for more events until the transaction is complete. Once the transaction is finished, the SQL thread can immediately instruct the I/O thread to rotate. (Bug #12400313, Bug #64503) References: See also Bug #13806492. * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored procedures on slave servers could cause replication failures. (Bug #12601974) * If the system time was adjusted backward during query execution, the apparent execution time could be negative. But in some cases these queries would be written to the slow query log, with the negative execution time written as a large unsigned number. Now statements with apparent negative execution time are not written to the slow query log. (Bug #63524, Bug #13454045) References: See also Bug #27208. * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * SHOW statements treated stored procedure, stored function, and event names as case sensitive. (Bug #56224, Bug #11763507) * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 14:59:39 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug11766634.result
Changes 5.1.62: * New utf8_general_mysql500_ci and ucs2_general_mysql500_ci collations have been added that preserve the behavior of utf8_general_ci and ucs2_general_ci from versions of MySQL previous to 5.1.24. Bug 27877 corrected an error in the original collations but introduced an incompatibility for columns that contain German 'ß' LATIN SMALL LETTER SHARP S. (As a result of the fix, that character compares equal to characters with which it previously compared different.) A symptom of the problem after upgrading to MySQL 5.1.24 or newer from a version older than 5.1.24 is that CHECK TABLE produces this error: * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Bugs Fixed
2012-04-08 21:10:58 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug12400341.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug13510739.result
Update mysql51-{client,server} to 5.1.63 (MySQL 5.1.63). Changes (http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html): * Security Fix: Bug #64884 was fixed. * Security Fix: Bug #59387 was fixed. * InnoDB: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. (Bug #13847885) * InnoDB: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. (Bug #12861864, Bug #11766019) * InnoDB: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. (Bug #11766634, Bug #59783) * Partitioning: After updating a row of a partitioned table and selecting that row within the same transaction with the query cache enabled, then performing a ROLLBACK, the same result was returned by an identical SELECT issued in a new transaction. (Bug #11761296, Bug #53775) * Replication: The --relay-log-space-limit option was sometimes ignored. More specifically, when the SQL thread went to sleep, it allowed the I/O thread to queue additional events in such a way that the relay log space limit was bypassed, and the number of events in the queue could grow well past the point where the relay logs needed to be rotated. Now in such cases, the SQL thread checks to see whether the I/O thread should rotate and provide the SQL thread a chance to purge the logs (thus freeing space). Note that, when the SQL thread is in the middle of a transaction, it cannot purge the logs; it can only ask for more events until the transaction is complete. Once the transaction is finished, the SQL thread can immediately instruct the I/O thread to rotate. (Bug #12400313, Bug #64503) References: See also Bug #13806492. * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored procedures on slave servers could cause replication failures. (Bug #12601974) * If the system time was adjusted backward during query execution, the apparent execution time could be negative. But in some cases these queries would be written to the slow query log, with the negative execution time written as a large unsigned number. Now statements with apparent negative execution time are not written to the slow query log. (Bug #63524, Bug #13454045) References: See also Bug #27208. * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * SHOW statements treated stored procedure, stored function, and event names as case sensitive. (Bug #56224, Bug #11763507) * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 14:59:39 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug13635833.result
Update mysql51 to 5.1.65. While here, let to use OpenSSL instead of internal yaSSL with ssl option, may related to PR 46912. Changes in MySQL 5.1.65 (2012-08-09) Functionality Added or Changed * Important Change: The YEAR(2) data type is now deprecated because it is problematic. Support for YEAR(2) will be removed in a future release of MySQL. For more information, see Section 11.3.4, "YEAR(2) Limitations and Migrating to YEAR(4)". Bugs Fixed * The server did not build with gcc 4.7. (Bug #14238406) Changes in MySQL 5.1.64 (Not released) Functionality Added or Changed * Important Change: Replication: The SHOW BINARY LOGS statement (and its equivalent SHOW MASTER LOGS) may now be executed by a user with the REPLICATION CLIENT privilege. (Formerly, the SUPER privilege was necessary to use either form of this statement.)
2012-09-15 16:48:57 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug14007649.result
Changes 5.1.71: Functionality Added or Changed * comp_err now checks to make sure that new errors are not being added to MySQL 5.1 or 5.5 because the set of errors for these series is frozen. Bugs Fixed * InnoDB: During an insert buffer merge, InnoDB would invoke lock_rec_restore_from_page_infimum() on a potentially invalid record pointer. * InnoDB: The page_zip_validate() consistency check would fail after compressing a page, in page_zip_compress(). This problem was caused by page_zip_decompress(), which would fail to set heap_no correctly when a record contained no user data bytes. A record with no user data bytes occurs when, for example, a primary key is an empty string and all secondary index fields are NULL or an empty string. * InnoDB: The pthread_mutex, commit_threads_m, which was initialized but never used, has been removed from the code base. * Partitioning: When dropping a partitioned table, the table's .par file was deleted first, before the table definition or data. This meant that, if the server failed during the drop operation, the table could be left in an inconsistent state in which it could neither be accessed nor dropped. * Shared-compatibility conflict errors occurred for RPM install operations, even if no shared-compatibility RPMs were already installed. * A user variable referenced during execution of a prepared statement is set to memory that is freed at the end of execution. A second execution of the statement could result in Valgrind warnings when accessing this memory. * Misoptimization of left expressions in prepared statements could cause a server exit. * Subsequent to Prepared statement needs to be re-prepared errors, inserts into DECIMAL columns caused a server exit. * Assigning the result of a subquery to a user variable raised an assertion when the outer query included DISTINCT and GROUP BY.
2013-08-04 12:20:24 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug14676111.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug21704.result
Update MySQL package to 5.1.56. Functionality added or changed: * mysqldump --xml now displays comments from column definitions. (Bug #13618) Bugs fixed: * InnoDB Storage Engine: InnoDB returned values for ¡Èrows examined¡É in the query plan that were higher than expected. NULL values were treated in an inconsistent way. The inaccurate statistics could trigger ¡Èfalse positives¡É in combination with the MAX_JOIN_SIZE setting, because the queries did not really examine as many rows as reported. (Bug #30423) * Partitioning: Trying to use the same column more than once in the partitioning key when partitioning a table by KEY caused mysqld to crash. Such duplication of key columns is now expressly disallowed, and fails with an appropriate error. (Bug #53354, Bug #57924) * Replication: When using the statement-based logging format, INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements affecting transactional tables that did not fail were not written to the binary log if they did not insert any rows. (With statement-based logging, all successful statements should be logged, whether they do or do not cause any rows to be changed.) (Bug #59338) * Replication: Formerly, STOP SLAVE stopped the slave I/O thread first and then stopped the slave SQL thread; thus, it was possible for the I/O thread to stop after replicating only part of a transaction which the SQL thread was executing, in wich case¡½if the transaction could not be rolled back safely¡½the SQL thread could hang. Now, STOP SLAVE stops the slave SQL thread first and then stops the I/O thread; this guarantees that the I/O thread can fetch any remaining events in the transaction that the SQL thread is executing, so that the SQL thread can finish the transaction if it cannot be rolled back safely. (Bug #58546) * A query of the following form returned an incorrect result, where the values for col_name in the result set were entirely replaced with NULL values: SELECT DISTINCT col_name ... ORDER BY col_name DESC; (Bug #59308, Bug #11766241) * DELETE or UPDATE statements could fail if they used DATE or DATETIME values with a year, month, or day part of zero. (Bug #59173) * The ESCAPE clause for the LIKE operator allows only expressions that evaluate to a constant at execution time, but aggregrate functions were not being rejected. (Bug #59149) * Memory leaks detected by Valgrind, some of which could cause incorrect query results, were corrected. (Bug #59110, Bug #11766075) mysqlslap failed to check for a NULL return from mysql_store_result() and crashed trying to process the result set. (Bug #59109) * In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could cause a server crash. (Bug #58371) * When mysqldadmin was run with the --sleep and --count options, it went into an infinite loop executing the specified command. (Bug #58221) * Some string manipulating SQL functions use a shared string object intended to contain an immutable empty string. This object was used by the SQL function SUBSTRING_INDEX() to return an empty string when one argument was of the wrong datatype. If the string object was then modified by the SQL function INSERT(), undefined behavior ensued. (Bug #58165, Bug #11765225) * Parsing nested regular expressions could lead to recursion resulting in a stack overflow crash. (Bug #58026, Bug #11765099) * The mysql client went into an infinite loop if the standard input was a directory. (Bug #57450) * The expression const1 BETWEEN const2 AND field was optimized incorrectly and produced incorrect results. (Bug #57030, Bug #11764215) * Some RPM installation scripts used a hardcoded value for the data directory, which could result in a failed installation for users who have a nonstandard data directory location. The same was true for other configuration values such as the PID file name. (Bug #56581, Bug #11763817) * On FreeBSD and OpenBSD, the server incorrectly checked the range of the system date, causing legal values to be rejected. (Bug #55755, Bug #11763089) * When using ExtractValue() or UpdateXML(), if the XML to be read contained an incomplete XML comment, MySQL read beyond the end of the XML string when processing, leading to a crash of the server. (Bug #44332)
2011-03-08 15:06:43 +01:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug30423.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug30919.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug34053.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug34300.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug35220.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug36169.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug36172.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug38231.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug39438.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug40360.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug40565.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug41904.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug42101-nonzero.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug42101.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug42419.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug44032.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug44369.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug44571.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug45357.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug46000.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug46676.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug47167.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug47621.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug47622.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug47777.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug48024.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug49164.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug51378.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug51920.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug52663.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug52745.result
Update mysql51-{client,server} package to 5.1.54. Functionality added or changed: * Support for the IBMDB2I storage engine has been removed. (Bug#58079) * The pstack library was nonfunctional and has been removed, along with the --with-pstack option for configure. The --enable-pstack option for mysqld is deprecated and will be removed in MySQL 5.5. (Bug#57210) Bugs fixed: * Performance: InnoDB Storage Engine: Improved concurrency when several ANALYZE TABLE or SHOW TABLE STATUS statements are run simultaneously for InnoDB tables. (Bug#53046) * InnoDB Storage Engine: For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#57799) * Partitioning: An INSERT ... ON DUPLICATE KEY UPDATE column = 0 statement on an AUTO_INCREMENT column caused the debug server to crash. (Bug#57890) * Several compilation problems were fixed. (Bug#57992, Bug#57993, Bug#57994, Bug#57995, Bug#57996, Bug#57997, Bug#58057) * Passing a string that was not null-terminated to UpdateXML() or ExtractValue() caused the server to fail with an assertion. (Bug#57279) * Queries executed using the Index Merge access method and a temporary file could return incorrect results. (Bug#56862) * The find_files() function used by SHOW statements performed redundant and unnecessary memory allocation. (Bug#51208)
2010-12-16 04:42:49 +01:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug53046.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug53290.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug53591.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug53592.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug53674.result
Update mysql51-{client,server} package from 5.1.51 to 5.1.52. This is maintainous release and pleare refer in detail: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html One note from the changes: * Security Fix: In prepared-statement mode, EXPLAIN for a SELECT from a derived table caused a server crash. (Bug#54488)
2010-11-04 16:57:07 +01:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug53756.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug54044.result
Update mysql51-{client,server} to 5.1.50. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-50.html for full changes . InnoDB Notes: InnoDB Plugin has been upgraded to version 1.0.11. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), generic Linux RPM packages, and any builds produced with the icc compiler. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: Important Change: Replication: The LOAD DATA INFILE statement is now considered unsafe for statement-based replication. When using statement-based logging mode, the statement now produces a warning; when using mixed-format logging, the statement is made using the row-based format. (Bug#34283) Partitioning: UPDATE and INSERT statements affecting partitioned tables performed poorly when using row-based replication. (Bug#52517) Partitioning: INSERT ON DUPLICATE KEY UPDATE statements performed poorly on tables having many partitions. This was because the handler function for reading a row from a specific index was not optimized in the partitioning handler. (Bug#52455) The server could crash on shutdown, if started with --innodb-use-system-malloc=0. (Bug#55581) GROUP BY operations used max_sort_length inconsistently. (Bug#55188) Building MySQL on Solaris 8 x86 failed when using Sun Studio due to gcc inline assembler code. (Bug#55061) In debug builds, an assertion could be raised when the server tried to send an OK packet to the client after having failed to detect errors during processing of the WHERE condition of an UPDATE statement. (Bug#54734) The database server could crash when renaming a table that had active transactions. (This issue only affected the database server when built for debugging.) (Bug#54453) The server could crash during the recovery phase of startup, if it previously crashed while inserting BLOB or other large columns that use off-page storage into an InnoDB table created with ROW_FORMAT=REDUNDANT or ROW_FORMAT=COMPACT. (Bug#54408) For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#54358) A client could supply data in chunks to a prepared statement parameter other than of type TEXT or BLOB using the mysql_stmt_send_long_data() C API function (or COM_STMT_SEND_LONG_DATA command). This led to a crash because other data types are not valid for long data. (Bug#54041) mysql_secure_installation did not properly identify local accounts and could incorrectly remove nonlocal root accounts. (Bug#54004) Transactions could be incorrectly committed during recovery, rather than rolled back, if the server crashed and was restarted after performing ALTER TABLE...ADD PRIMARY KEY on an InnoDB table, or some other operation that involves copying the entire table. (Bug#53756) Portability problems in SHOW STATUS could lead to incorrect results on some platforms. (Bug#53493) Builds of MySQL generated a large number of warnings. (Bug#53445) With lower_case_table_names set to a nonzero value, searches for table or database names in INFORMATION_SCHEMA tables could produce incorrect results. (Bug#53095) The ABI check for MySQL failed to compile with gcc 4.5. (Bug#52514) mysql_secure_installation sometimes failed to locate the mysql client. (Bug#52274) Reading a ucs2 data file with LOAD DATA INFILE was subject to three problems. 1) Incorrect parsing of the file as ucs2 data, resulting in incorrect length of the parsed string. This is fixed by truncating the invalid trailing bytes (incomplete multibyte characters) when reading from the file. 2) Reads from a proper ucs2 file did not recognize newline characters. This is fixed by first checking whether a byte is a newline (or any other special character) before reading it as a part of a multibyte character. 3) When using user variables to hold column data, the character set of the user variable was set incorrectly to the database charset. This is fixed by setting it to the character set specified in the LOAD DATA INFILE statement, if any. (Bug#51876) Searches in INFORMATION_SCHEMA tables for rows matching a nonexistent database produced an error instead of an empty query result. (Bug#49542) On FreeBSD, memory mapping for MERGE tables could fail if underlying tables were empty. (Bug#47139) The my_like_range_xxx() functions returned badly formed maximum strings for Asian character sets, which caused problems for storage engines. (Bug#45012) A debugging assertion could be raised after a write failure to a closed socket. (Bug#42496) An assertion failure occurred within yaSSL for very long keys. (Bug#29784) See also Bug#53463.
2010-09-08 18:24:57 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug54453.result
Update mysql51-{client,server} to 5.1.53. Most changes are related to replication and seems to no security fix. For more detail, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html
2010-11-26 14:52:58 +01:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug56143.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug56680.result
Update mysql51-{client,server} package from 5.1.51 to 5.1.52. This is maintainous release and pleare refer in detail: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html One note from the changes: * Security Fix: In prepared-statement mode, EXPLAIN for a SELECT from a derived table caused a server crash. (Bug#54488)
2010-11-04 16:57:07 +01:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug56716.result
Update mysql51-{client,server} to 5.1.53. Most changes are related to replication and seems to no security fix. For more detail, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html
2010-11-26 14:52:58 +01:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug56947.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug57252.result
Update mysql51-{client,server} package from 5.1.51 to 5.1.52. This is maintainous release and pleare refer in detail: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html One note from the changes: * Security Fix: In prepared-statement mode, EXPLAIN for a SELECT from a derived table caused a server crash. (Bug#54488)
2010-11-04 16:57:07 +01:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug57255.result
Update mysql51-{client,server} package to 5.1.57. This is simply maintenance release, no security fix. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-57.html in detail.
2011-05-08 18:01:57 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug59307.result
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug59410.result
share/mysql-test/suite/innodb_plugin/r/innodb_bug59641.result
Update mysql51-{client,server} package to 5.1.57. This is simply maintenance release, no security fix. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-57.html in detail.
2011-05-08 18:01:57 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_bug60049.result
Changes 5.1.61: * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. * An incorrect InnoDB assertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source file btr0pcur.ic and the variable cursor->pos_state. * The handle_segfault() signal-handler code in mysqld could itself crash due to calling unsafe functions. * ARCHIVE tables with NULL columns could cause server crashes or become corrupt under concurrent load. * Enabling myisam_use_mmap could cause the server to crash. * Concurrent access to ARCHIVE tables could cause corruption.
2012-01-12 18:41:21 +01:00
share/mysql-test/suite/innodb_plugin/r/innodb_cmp_drop_table.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_file_format.result
share/mysql-test/suite/innodb_plugin/r/innodb_gis.result
share/mysql-test/suite/innodb_plugin/r/innodb_information_schema.result
Changes 5.1.67: Bug fixes http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-67.html
2013-01-21 09:58:43 +01:00
share/mysql-test/suite/innodb_plugin/r/innodb_information_schema_buffer.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_lock_wait_timeout_1.result
Changes 5.1.60: * Upgrading from an Advanced GPL RPM package to an Advanced RPM package did not work. Now on Linux it is possible to use rpm -U to replace any installed MySQL product by any other of the same release family. It is not necessary to remove the old produce with rpm -e first. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. Bugs Fixed * Important Change: InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Replication: Issuing the following statements, in the order shown, could cause a deadlock between the user thread and I/O thread. * more...
2011-12-02 15:25:09 +01:00
share/mysql-test/suite/innodb_plugin/r/innodb_misc1.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_multi_update.result
share/mysql-test/suite/innodb_plugin/r/innodb_mysql.result
share/mysql-test/suite/innodb_plugin/r/innodb_mysql_rbk.result
share/mysql-test/suite/innodb_plugin/r/innodb_notembedded.result
Changes 5.1.61: * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. * An incorrect InnoDB assertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source file btr0pcur.ic and the variable cursor->pos_state. * The handle_segfault() signal-handler code in mysqld could itself crash due to calling unsafe functions. * ARCHIVE tables with NULL columns could cause server crashes or become corrupt under concurrent load. * Enabling myisam_use_mmap could cause the server to crash. * Concurrent access to ARCHIVE tables could cause corruption.
2012-01-12 18:41:21 +01:00
share/mysql-test/suite/innodb_plugin/r/innodb_replace.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/r/innodb_timeout_rollback.result
share/mysql-test/suite/innodb_plugin/r/innodb_trx_weight.result
share/mysql-test/suite/innodb_plugin/t/disabled.def
share/mysql-test/suite/innodb_plugin/t/innodb-analyze.test
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb-autoinc-18274.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb-autoinc-44030.test
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb-autoinc-56228-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb-autoinc-56228.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb-autoinc-optimize.test
share/mysql-test/suite/innodb_plugin/t/innodb-autoinc.test
Changes 5.1.62: * New utf8_general_mysql500_ci and ucs2_general_mysql500_ci collations have been added that preserve the behavior of utf8_general_ci and ucs2_general_ci from versions of MySQL previous to 5.1.24. Bug 27877 corrected an error in the original collations but introduced an incompatibility for columns that contain German 'ß' LATIN SMALL LETTER SHARP S. (As a result of the fix, that character compares equal to characters with which it previously compared different.) A symptom of the problem after upgrading to MySQL 5.1.24 or newer from a version older than 5.1.24 is that CHECK TABLE produces this error: * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Bugs Fixed
2012-04-08 21:10:58 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb-blob.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb-consistent-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb-consistent.test
Update mysql51-{client,server} package to 5.1.54. Functionality added or changed: * Support for the IBMDB2I storage engine has been removed. (Bug#58079) * The pstack library was nonfunctional and has been removed, along with the --with-pstack option for configure. The --enable-pstack option for mysqld is deprecated and will be removed in MySQL 5.5. (Bug#57210) Bugs fixed: * Performance: InnoDB Storage Engine: Improved concurrency when several ANALYZE TABLE or SHOW TABLE STATUS statements are run simultaneously for InnoDB tables. (Bug#53046) * InnoDB Storage Engine: For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#57799) * Partitioning: An INSERT ... ON DUPLICATE KEY UPDATE column = 0 statement on an AUTO_INCREMENT column caused the debug server to crash. (Bug#57890) * Several compilation problems were fixed. (Bug#57992, Bug#57993, Bug#57994, Bug#57995, Bug#57996, Bug#57997, Bug#58057) * Passing a string that was not null-terminated to UpdateXML() or ExtractValue() caused the server to fail with an assertion. (Bug#57279) * Queries executed using the Index Merge access method and a temporary file could return incorrect results. (Bug#56862) * The find_files() function used by SHOW statements performed redundant and unnecessary memory allocation. (Bug#51208)
2010-12-16 04:42:49 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb-create-options.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb-index.test
share/mysql-test/suite/innodb_plugin/t/innodb-index_ucs2.test
share/mysql-test/suite/innodb_plugin/t/innodb-lock.test
share/mysql-test/suite/innodb_plugin/t/innodb-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb-replace.test
share/mysql-test/suite/innodb_plugin/t/innodb-semi-consistent-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb-semi-consistent.test
share/mysql-test/suite/innodb_plugin/t/innodb-timeout.test
share/mysql-test/suite/innodb_plugin/t/innodb-ucs2.test
share/mysql-test/suite/innodb_plugin/t/innodb-use-sys-malloc-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb-use-sys-malloc.test
share/mysql-test/suite/innodb_plugin/t/innodb-zip.test
share/mysql-test/suite/innodb_plugin/t/innodb.test
share/mysql-test/suite/innodb_plugin/t/innodb_autoinc_lock_mode_zero-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb_autoinc_lock_mode_zero.test
Changes 5.1.62: * New utf8_general_mysql500_ci and ucs2_general_mysql500_ci collations have been added that preserve the behavior of utf8_general_ci and ucs2_general_ci from versions of MySQL previous to 5.1.24. Bug 27877 corrected an error in the original collations but introduced an incompatibility for columns that contain German 'ß' LATIN SMALL LETTER SHARP S. (As a result of the fix, that character compares equal to characters with which it previously compared different.) A symptom of the problem after upgrading to MySQL 5.1.24 or newer from a version older than 5.1.24 is that CHECK TABLE produces this error: * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Bugs Fixed
2012-04-08 21:10:58 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug11754376.test
Update mysql51-{client,server} to 5.1.63 (MySQL 5.1.63). Changes (http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html): * Security Fix: Bug #64884 was fixed. * Security Fix: Bug #59387 was fixed. * InnoDB: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. (Bug #13847885) * InnoDB: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. (Bug #12861864, Bug #11766019) * InnoDB: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. (Bug #11766634, Bug #59783) * Partitioning: After updating a row of a partitioned table and selecting that row within the same transaction with the query cache enabled, then performing a ROLLBACK, the same result was returned by an identical SELECT issued in a new transaction. (Bug #11761296, Bug #53775) * Replication: The --relay-log-space-limit option was sometimes ignored. More specifically, when the SQL thread went to sleep, it allowed the I/O thread to queue additional events in such a way that the relay log space limit was bypassed, and the number of events in the queue could grow well past the point where the relay logs needed to be rotated. Now in such cases, the SQL thread checks to see whether the I/O thread should rotate and provide the SQL thread a chance to purge the logs (thus freeing space). Note that, when the SQL thread is in the middle of a transaction, it cannot purge the logs; it can only ask for more events until the transaction is complete. Once the transaction is finished, the SQL thread can immediately instruct the I/O thread to rotate. (Bug #12400313, Bug #64503) References: See also Bug #13806492. * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored procedures on slave servers could cause replication failures. (Bug #12601974) * If the system time was adjusted backward during query execution, the apparent execution time could be negative. But in some cases these queries would be written to the slow query log, with the negative execution time written as a large unsigned number. Now statements with apparent negative execution time are not written to the slow query log. (Bug #63524, Bug #13454045) References: See also Bug #27208. * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * SHOW statements treated stored procedure, stored function, and event names as case sensitive. (Bug #56224, Bug #11763507) * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 14:59:39 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug11766634.test
Changes 5.1.62: * New utf8_general_mysql500_ci and ucs2_general_mysql500_ci collations have been added that preserve the behavior of utf8_general_ci and ucs2_general_ci from versions of MySQL previous to 5.1.24. Bug 27877 corrected an error in the original collations but introduced an incompatibility for columns that contain German 'ß' LATIN SMALL LETTER SHARP S. (As a result of the fix, that character compares equal to characters with which it previously compared different.) A symptom of the problem after upgrading to MySQL 5.1.24 or newer from a version older than 5.1.24 is that CHECK TABLE produces this error: * yaSSL was upgraded from version 1.7.2 to 2.2.0. * Bugs Fixed
2012-04-08 21:10:58 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug12400341-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb_bug12400341.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug13510739.test
Update mysql51-{client,server} to 5.1.63 (MySQL 5.1.63). Changes (http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html): * Security Fix: Bug #64884 was fixed. * Security Fix: Bug #59387 was fixed. * InnoDB: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. (Bug #13847885) * InnoDB: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. (Bug #12861864, Bug #11766019) * InnoDB: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. (Bug #11766634, Bug #59783) * Partitioning: After updating a row of a partitioned table and selecting that row within the same transaction with the query cache enabled, then performing a ROLLBACK, the same result was returned by an identical SELECT issued in a new transaction. (Bug #11761296, Bug #53775) * Replication: The --relay-log-space-limit option was sometimes ignored. More specifically, when the SQL thread went to sleep, it allowed the I/O thread to queue additional events in such a way that the relay log space limit was bypassed, and the number of events in the queue could grow well past the point where the relay logs needed to be rotated. Now in such cases, the SQL thread checks to see whether the I/O thread should rotate and provide the SQL thread a chance to purge the logs (thus freeing space). Note that, when the SQL thread is in the middle of a transaction, it cannot purge the logs; it can only ask for more events until the transaction is complete. Once the transaction is finished, the SQL thread can immediately instruct the I/O thread to rotate. (Bug #12400313, Bug #64503) References: See also Bug #13806492. * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored procedures on slave servers could cause replication failures. (Bug #12601974) * If the system time was adjusted backward during query execution, the apparent execution time could be negative. But in some cases these queries would be written to the slow query log, with the negative execution time written as a large unsigned number. Now statements with apparent negative execution time are not written to the slow query log. (Bug #63524, Bug #13454045) References: See also Bug #27208. * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * SHOW statements treated stored procedure, stored function, and event names as case sensitive. (Bug #56224, Bug #11763507) * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 14:59:39 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug13635833.test
Update mysql51 to 5.1.65. While here, let to use OpenSSL instead of internal yaSSL with ssl option, may related to PR 46912. Changes in MySQL 5.1.65 (2012-08-09) Functionality Added or Changed * Important Change: The YEAR(2) data type is now deprecated because it is problematic. Support for YEAR(2) will be removed in a future release of MySQL. For more information, see Section 11.3.4, "YEAR(2) Limitations and Migrating to YEAR(4)". Bugs Fixed * The server did not build with gcc 4.7. (Bug #14238406) Changes in MySQL 5.1.64 (Not released) Functionality Added or Changed * Important Change: Replication: The SHOW BINARY LOGS statement (and its equivalent SHOW MASTER LOGS) may now be executed by a user with the REPLICATION CLIENT privilege. (Formerly, the SUPER privilege was necessary to use either form of this statement.)
2012-09-15 16:48:57 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug14007649.test
Changes 5.1.71: Functionality Added or Changed * comp_err now checks to make sure that new errors are not being added to MySQL 5.1 or 5.5 because the set of errors for these series is frozen. Bugs Fixed * InnoDB: During an insert buffer merge, InnoDB would invoke lock_rec_restore_from_page_infimum() on a potentially invalid record pointer. * InnoDB: The page_zip_validate() consistency check would fail after compressing a page, in page_zip_compress(). This problem was caused by page_zip_decompress(), which would fail to set heap_no correctly when a record contained no user data bytes. A record with no user data bytes occurs when, for example, a primary key is an empty string and all secondary index fields are NULL or an empty string. * InnoDB: The pthread_mutex, commit_threads_m, which was initialized but never used, has been removed from the code base. * Partitioning: When dropping a partitioned table, the table's .par file was deleted first, before the table definition or data. This meant that, if the server failed during the drop operation, the table could be left in an inconsistent state in which it could neither be accessed nor dropped. * Shared-compatibility conflict errors occurred for RPM install operations, even if no shared-compatibility RPMs were already installed. * A user variable referenced during execution of a prepared statement is set to memory that is freed at the end of execution. A second execution of the statement could result in Valgrind warnings when accessing this memory. * Misoptimization of left expressions in prepared statements could cause a server exit. * Subsequent to Prepared statement needs to be re-prepared errors, inserts into DECIMAL columns caused a server exit. * Assigning the result of a subquery to a user variable raised an assertion when the outer query included DISTINCT and GROUP BY.
2013-08-04 12:20:24 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug14676111.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug21704.test
Update MySQL package to 5.1.56. Functionality added or changed: * mysqldump --xml now displays comments from column definitions. (Bug #13618) Bugs fixed: * InnoDB Storage Engine: InnoDB returned values for ¡Èrows examined¡É in the query plan that were higher than expected. NULL values were treated in an inconsistent way. The inaccurate statistics could trigger ¡Èfalse positives¡É in combination with the MAX_JOIN_SIZE setting, because the queries did not really examine as many rows as reported. (Bug #30423) * Partitioning: Trying to use the same column more than once in the partitioning key when partitioning a table by KEY caused mysqld to crash. Such duplication of key columns is now expressly disallowed, and fails with an appropriate error. (Bug #53354, Bug #57924) * Replication: When using the statement-based logging format, INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements affecting transactional tables that did not fail were not written to the binary log if they did not insert any rows. (With statement-based logging, all successful statements should be logged, whether they do or do not cause any rows to be changed.) (Bug #59338) * Replication: Formerly, STOP SLAVE stopped the slave I/O thread first and then stopped the slave SQL thread; thus, it was possible for the I/O thread to stop after replicating only part of a transaction which the SQL thread was executing, in wich case¡½if the transaction could not be rolled back safely¡½the SQL thread could hang. Now, STOP SLAVE stops the slave SQL thread first and then stops the I/O thread; this guarantees that the I/O thread can fetch any remaining events in the transaction that the SQL thread is executing, so that the SQL thread can finish the transaction if it cannot be rolled back safely. (Bug #58546) * A query of the following form returned an incorrect result, where the values for col_name in the result set were entirely replaced with NULL values: SELECT DISTINCT col_name ... ORDER BY col_name DESC; (Bug #59308, Bug #11766241) * DELETE or UPDATE statements could fail if they used DATE or DATETIME values with a year, month, or day part of zero. (Bug #59173) * The ESCAPE clause for the LIKE operator allows only expressions that evaluate to a constant at execution time, but aggregrate functions were not being rejected. (Bug #59149) * Memory leaks detected by Valgrind, some of which could cause incorrect query results, were corrected. (Bug #59110, Bug #11766075) mysqlslap failed to check for a NULL return from mysql_store_result() and crashed trying to process the result set. (Bug #59109) * In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could cause a server crash. (Bug #58371) * When mysqldadmin was run with the --sleep and --count options, it went into an infinite loop executing the specified command. (Bug #58221) * Some string manipulating SQL functions use a shared string object intended to contain an immutable empty string. This object was used by the SQL function SUBSTRING_INDEX() to return an empty string when one argument was of the wrong datatype. If the string object was then modified by the SQL function INSERT(), undefined behavior ensued. (Bug #58165, Bug #11765225) * Parsing nested regular expressions could lead to recursion resulting in a stack overflow crash. (Bug #58026, Bug #11765099) * The mysql client went into an infinite loop if the standard input was a directory. (Bug #57450) * The expression const1 BETWEEN const2 AND field was optimized incorrectly and produced incorrect results. (Bug #57030, Bug #11764215) * Some RPM installation scripts used a hardcoded value for the data directory, which could result in a failed installation for users who have a nonstandard data directory location. The same was true for other configuration values such as the PID file name. (Bug #56581, Bug #11763817) * On FreeBSD and OpenBSD, the server incorrectly checked the range of the system date, causing legal values to be rejected. (Bug #55755, Bug #11763089) * When using ExtractValue() or UpdateXML(), if the XML to be read contained an incomplete XML comment, MySQL read beyond the end of the XML string when processing, leading to a crash of the server. (Bug #44332)
2011-03-08 15:06:43 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug30423.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug30919-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb_bug30919.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug34053.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug34300.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug35220.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug36169.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug36172.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug38231.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug39438-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb_bug39438.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug40360.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug40565.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug41904.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug42101-nonzero-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb_bug42101-nonzero.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug42101.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug42419.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug44032.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug44369.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug44571.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug45357.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug46000.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug46676.test
Changes 5.1.60: * Upgrading from an Advanced GPL RPM package to an Advanced RPM package did not work. Now on Linux it is possible to use rpm -U to replace any installed MySQL product by any other of the same release family. It is not necessary to remove the old produce with rpm -e first. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. Bugs Fixed * Important Change: InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Replication: Issuing the following statements, in the order shown, could cause a deadlock between the user thread and I/O thread. * more...
2011-12-02 15:25:09 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug47167-master.opt
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug47167.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug47621.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug47622.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug47777.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug48024.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug49164.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug51378.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug51920.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug52663.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug52745.test
Update mysql51-{client,server} package to 5.1.54. Functionality added or changed: * Support for the IBMDB2I storage engine has been removed. (Bug#58079) * The pstack library was nonfunctional and has been removed, along with the --with-pstack option for configure. The --enable-pstack option for mysqld is deprecated and will be removed in MySQL 5.5. (Bug#57210) Bugs fixed: * Performance: InnoDB Storage Engine: Improved concurrency when several ANALYZE TABLE or SHOW TABLE STATUS statements are run simultaneously for InnoDB tables. (Bug#53046) * InnoDB Storage Engine: For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#57799) * Partitioning: An INSERT ... ON DUPLICATE KEY UPDATE column = 0 statement on an AUTO_INCREMENT column caused the debug server to crash. (Bug#57890) * Several compilation problems were fixed. (Bug#57992, Bug#57993, Bug#57994, Bug#57995, Bug#57996, Bug#57997, Bug#58057) * Passing a string that was not null-terminated to UpdateXML() or ExtractValue() caused the server to fail with an assertion. (Bug#57279) * Queries executed using the Index Merge access method and a temporary file could return incorrect results. (Bug#56862) * The find_files() function used by SHOW statements performed redundant and unnecessary memory allocation. (Bug#51208)
2010-12-16 04:42:49 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug53046.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug53290.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug53591.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug53592.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug53674-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb_bug53674.test
Update mysql51-{client,server} package from 5.1.51 to 5.1.52. This is maintainous release and pleare refer in detail: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html One note from the changes: * Security Fix: In prepared-statement mode, EXPLAIN for a SELECT from a derived table caused a server crash. (Bug#54488)
2010-11-04 16:57:07 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug53756-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb_bug53756.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug54044.test
Update mysql51-{client,server} to 5.1.50. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-50.html for full changes . InnoDB Notes: InnoDB Plugin has been upgraded to version 1.0.11. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), generic Linux RPM packages, and any builds produced with the icc compiler. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: Important Change: Replication: The LOAD DATA INFILE statement is now considered unsafe for statement-based replication. When using statement-based logging mode, the statement now produces a warning; when using mixed-format logging, the statement is made using the row-based format. (Bug#34283) Partitioning: UPDATE and INSERT statements affecting partitioned tables performed poorly when using row-based replication. (Bug#52517) Partitioning: INSERT ON DUPLICATE KEY UPDATE statements performed poorly on tables having many partitions. This was because the handler function for reading a row from a specific index was not optimized in the partitioning handler. (Bug#52455) The server could crash on shutdown, if started with --innodb-use-system-malloc=0. (Bug#55581) GROUP BY operations used max_sort_length inconsistently. (Bug#55188) Building MySQL on Solaris 8 x86 failed when using Sun Studio due to gcc inline assembler code. (Bug#55061) In debug builds, an assertion could be raised when the server tried to send an OK packet to the client after having failed to detect errors during processing of the WHERE condition of an UPDATE statement. (Bug#54734) The database server could crash when renaming a table that had active transactions. (This issue only affected the database server when built for debugging.) (Bug#54453) The server could crash during the recovery phase of startup, if it previously crashed while inserting BLOB or other large columns that use off-page storage into an InnoDB table created with ROW_FORMAT=REDUNDANT or ROW_FORMAT=COMPACT. (Bug#54408) For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#54358) A client could supply data in chunks to a prepared statement parameter other than of type TEXT or BLOB using the mysql_stmt_send_long_data() C API function (or COM_STMT_SEND_LONG_DATA command). This led to a crash because other data types are not valid for long data. (Bug#54041) mysql_secure_installation did not properly identify local accounts and could incorrectly remove nonlocal root accounts. (Bug#54004) Transactions could be incorrectly committed during recovery, rather than rolled back, if the server crashed and was restarted after performing ALTER TABLE...ADD PRIMARY KEY on an InnoDB table, or some other operation that involves copying the entire table. (Bug#53756) Portability problems in SHOW STATUS could lead to incorrect results on some platforms. (Bug#53493) Builds of MySQL generated a large number of warnings. (Bug#53445) With lower_case_table_names set to a nonzero value, searches for table or database names in INFORMATION_SCHEMA tables could produce incorrect results. (Bug#53095) The ABI check for MySQL failed to compile with gcc 4.5. (Bug#52514) mysql_secure_installation sometimes failed to locate the mysql client. (Bug#52274) Reading a ucs2 data file with LOAD DATA INFILE was subject to three problems. 1) Incorrect parsing of the file as ucs2 data, resulting in incorrect length of the parsed string. This is fixed by truncating the invalid trailing bytes (incomplete multibyte characters) when reading from the file. 2) Reads from a proper ucs2 file did not recognize newline characters. This is fixed by first checking whether a byte is a newline (or any other special character) before reading it as a part of a multibyte character. 3) When using user variables to hold column data, the character set of the user variable was set incorrectly to the database charset. This is fixed by setting it to the character set specified in the LOAD DATA INFILE statement, if any. (Bug#51876) Searches in INFORMATION_SCHEMA tables for rows matching a nonexistent database produced an error instead of an empty query result. (Bug#49542) On FreeBSD, memory mapping for MERGE tables could fail if underlying tables were empty. (Bug#47139) The my_like_range_xxx() functions returned badly formed maximum strings for Asian character sets, which caused problems for storage engines. (Bug#45012) A debugging assertion could be raised after a write failure to a closed socket. (Bug#42496) An assertion failure occurred within yaSSL for very long keys. (Bug#29784) See also Bug#53463.
2010-09-08 18:24:57 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug54453.test
Update mysql51-{client,server} to 5.1.53. Most changes are related to replication and seems to no security fix. For more detail, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html
2010-11-26 14:52:58 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug56143.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug56680.test
Update mysql51-{client,server} package from 5.1.51 to 5.1.52. This is maintainous release and pleare refer in detail: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html One note from the changes: * Security Fix: In prepared-statement mode, EXPLAIN for a SELECT from a derived table caused a server crash. (Bug#54488)
2010-11-04 16:57:07 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug56716.test
Update mysql51-{client,server} to 5.1.53. Most changes are related to replication and seems to no security fix. For more detail, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html
2010-11-26 14:52:58 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug56947.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug57252.test
Update mysql51-{client,server} package from 5.1.51 to 5.1.52. This is maintainous release and pleare refer in detail: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html One note from the changes: * Security Fix: In prepared-statement mode, EXPLAIN for a SELECT from a derived table caused a server crash. (Bug#54488)
2010-11-04 16:57:07 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug57255.test
Update mysql51-{client,server} package to 5.1.57. This is simply maintenance release, no security fix. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-57.html in detail.
2011-05-08 18:01:57 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug59307.test
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug59410.test
share/mysql-test/suite/innodb_plugin/t/innodb_bug59641.test
Update mysql51-{client,server} package to 5.1.57. This is simply maintenance release, no security fix. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-57.html in detail.
2011-05-08 18:01:57 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_bug60049-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb_bug60049.test
Changes 5.1.61: * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. * An incorrect InnoDB assertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source file btr0pcur.ic and the variable cursor->pos_state. * The handle_segfault() signal-handler code in mysqld could itself crash due to calling unsafe functions. * ARCHIVE tables with NULL columns could cause server crashes or become corrupt under concurrent load. * Enabling myisam_use_mmap could cause the server to crash. * Concurrent access to ARCHIVE tables could cause corruption.
2012-01-12 18:41:21 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb_cmp_drop_table-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb_cmp_drop_table.test
Changes 5.1.60: * Upgrading from an Advanced GPL RPM package to an Advanced RPM package did not work. Now on Linux it is possible to use rpm -U to replace any installed MySQL product by any other of the same release family. It is not necessary to remove the old produce with rpm -e first. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. Bugs Fixed * Important Change: InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Replication: Issuing the following statements, in the order shown, could cause a deadlock between the user thread and I/O thread. * more...
2011-12-02 15:25:09 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb_file_format-master.opt
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_file_format.test
share/mysql-test/suite/innodb_plugin/t/innodb_gis.test
share/mysql-test/suite/innodb_plugin/t/innodb_information_schema.test
Changes 5.1.67: Bug fixes http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-67.html
2013-01-21 09:58:43 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb_information_schema_buffer.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_lock_wait_timeout_1-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb_lock_wait_timeout_1.test
Changes 5.1.60: * Upgrading from an Advanced GPL RPM package to an Advanced RPM package did not work. Now on Linux it is possible to use rpm -U to replace any installed MySQL product by any other of the same release family. It is not necessary to remove the old produce with rpm -e first. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. Bugs Fixed * Important Change: InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Replication: Issuing the following statements, in the order shown, could cause a deadlock between the user thread and I/O thread. * more...
2011-12-02 15:25:09 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb_misc1-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb_misc1.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_multi_update.test
share/mysql-test/suite/innodb_plugin/t/innodb_mysql-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb_mysql.test
share/mysql-test/suite/innodb_plugin/t/innodb_mysql_rbk-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb_mysql_rbk.test
share/mysql-test/suite/innodb_plugin/t/innodb_notembedded.test
Changes 5.1.61: * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. * An incorrect InnoDB assertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source file btr0pcur.ic and the variable cursor->pos_state. * The handle_segfault() signal-handler code in mysqld could itself crash due to calling unsafe functions. * ARCHIVE tables with NULL columns could cause server crashes or become corrupt under concurrent load. * Enabling myisam_use_mmap could cause the server to crash. * Concurrent access to ARCHIVE tables could cause corruption.
2012-01-12 18:41:21 +01:00
share/mysql-test/suite/innodb_plugin/t/innodb_replace.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/innodb_plugin/t/innodb_timeout_rollback-master.opt
share/mysql-test/suite/innodb_plugin/t/innodb_timeout_rollback.test
share/mysql-test/suite/innodb_plugin/t/innodb_trx_weight.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/jp/include/trim_sjis.inc
share/mysql-test/suite/jp/r/jp_alter_sjis.result
share/mysql-test/suite/jp/r/jp_alter_ucs2.result
share/mysql-test/suite/jp/r/jp_alter_ujis.result
share/mysql-test/suite/jp/r/jp_alter_utf8.result
share/mysql-test/suite/jp/r/jp_charlength_sjis.result
share/mysql-test/suite/jp/r/jp_charlength_ucs2.result
share/mysql-test/suite/jp/r/jp_charlength_ujis.result
share/mysql-test/suite/jp/r/jp_charlength_utf8.result
share/mysql-test/suite/jp/r/jp_charset_sjis.result
share/mysql-test/suite/jp/r/jp_charset_ucs2.result
share/mysql-test/suite/jp/r/jp_charset_ujis.result
share/mysql-test/suite/jp/r/jp_charset_utf8.result
share/mysql-test/suite/jp/r/jp_convert_sjis.result
share/mysql-test/suite/jp/r/jp_convert_ucs2.result
share/mysql-test/suite/jp/r/jp_convert_ujis.result
share/mysql-test/suite/jp/r/jp_convert_utf8.result
share/mysql-test/suite/jp/r/jp_create_db_sjis.result
share/mysql-test/suite/jp/r/jp_create_db_ucs2.result
share/mysql-test/suite/jp/r/jp_create_db_ujis.result
share/mysql-test/suite/jp/r/jp_create_db_utf8.result
share/mysql-test/suite/jp/r/jp_create_tbl_sjis.result
share/mysql-test/suite/jp/r/jp_create_tbl_ucs2.result
share/mysql-test/suite/jp/r/jp_create_tbl_ujis.result
share/mysql-test/suite/jp/r/jp_create_tbl_utf8.result
share/mysql-test/suite/jp/r/jp_enum_sjis.result
share/mysql-test/suite/jp/r/jp_enum_ucs2.result
share/mysql-test/suite/jp/r/jp_enum_ujis.result
share/mysql-test/suite/jp/r/jp_enum_utf8.result
share/mysql-test/suite/jp/r/jp_insert_sjis.result
share/mysql-test/suite/jp/r/jp_insert_ucs2.result
share/mysql-test/suite/jp/r/jp_insert_ujis.result
share/mysql-test/suite/jp/r/jp_insert_utf8.result
share/mysql-test/suite/jp/r/jp_instr_sjis.result
share/mysql-test/suite/jp/r/jp_instr_ucs2.result
share/mysql-test/suite/jp/r/jp_instr_ujis.result
share/mysql-test/suite/jp/r/jp_instr_utf8.result
share/mysql-test/suite/jp/r/jp_join_sjis.result
share/mysql-test/suite/jp/r/jp_join_ucs2.result
share/mysql-test/suite/jp/r/jp_join_ujis.result
share/mysql-test/suite/jp/r/jp_join_utf8.result
share/mysql-test/suite/jp/r/jp_left_sjis.result
share/mysql-test/suite/jp/r/jp_left_ucs2.result
share/mysql-test/suite/jp/r/jp_left_ujis.result
share/mysql-test/suite/jp/r/jp_left_utf8.result
share/mysql-test/suite/jp/r/jp_length_sjis.result
share/mysql-test/suite/jp/r/jp_length_ucs2.result
share/mysql-test/suite/jp/r/jp_length_ujis.result
share/mysql-test/suite/jp/r/jp_length_utf8.result
share/mysql-test/suite/jp/r/jp_like_sjis.result
share/mysql-test/suite/jp/r/jp_like_ucs2.result
share/mysql-test/suite/jp/r/jp_like_ujis.result
share/mysql-test/suite/jp/r/jp_like_utf8.result
share/mysql-test/suite/jp/r/jp_locate_sjis.result
share/mysql-test/suite/jp/r/jp_locate_ucs2.result
share/mysql-test/suite/jp/r/jp_locate_ujis.result
share/mysql-test/suite/jp/r/jp_locate_utf8.result
share/mysql-test/suite/jp/r/jp_lpad_sjis.result
share/mysql-test/suite/jp/r/jp_lpad_ucs2.result
share/mysql-test/suite/jp/r/jp_lpad_ujis.result
share/mysql-test/suite/jp/r/jp_lpad_utf8.result
share/mysql-test/suite/jp/r/jp_ltrim_sjis.result
share/mysql-test/suite/jp/r/jp_ltrim_ucs2.result
share/mysql-test/suite/jp/r/jp_ltrim_ujis.result
share/mysql-test/suite/jp/r/jp_ltrim_utf8.result
share/mysql-test/suite/jp/r/jp_ps_sjis.result
share/mysql-test/suite/jp/r/jp_ps_ujis.result
share/mysql-test/suite/jp/r/jp_replace_sjis.result
share/mysql-test/suite/jp/r/jp_replace_ucs2.result
share/mysql-test/suite/jp/r/jp_replace_ujis.result
share/mysql-test/suite/jp/r/jp_replace_utf8.result
share/mysql-test/suite/jp/r/jp_reverse_sjis.result
share/mysql-test/suite/jp/r/jp_reverse_ucs2.result
share/mysql-test/suite/jp/r/jp_reverse_ujis.result
share/mysql-test/suite/jp/r/jp_reverse_utf8.result
share/mysql-test/suite/jp/r/jp_right_sjis.result
share/mysql-test/suite/jp/r/jp_right_ucs2.result
share/mysql-test/suite/jp/r/jp_right_ujis.result
share/mysql-test/suite/jp/r/jp_right_utf8.result
share/mysql-test/suite/jp/r/jp_rpad_sjis.result
share/mysql-test/suite/jp/r/jp_rpad_ucs2.result
share/mysql-test/suite/jp/r/jp_rpad_ujis.result
share/mysql-test/suite/jp/r/jp_rpad_utf8.result
share/mysql-test/suite/jp/r/jp_rtrim_sjis.result
share/mysql-test/suite/jp/r/jp_rtrim_ucs2.result
share/mysql-test/suite/jp/r/jp_rtrim_ujis.result
share/mysql-test/suite/jp/r/jp_rtrim_utf8.result
share/mysql-test/suite/jp/r/jp_select_sjis.result
share/mysql-test/suite/jp/r/jp_select_ucs2.result
share/mysql-test/suite/jp/r/jp_select_ujis.result
share/mysql-test/suite/jp/r/jp_select_utf8.result
share/mysql-test/suite/jp/r/jp_subquery_sjis.result
share/mysql-test/suite/jp/r/jp_subquery_ucs2.result
share/mysql-test/suite/jp/r/jp_subquery_ujis.result
share/mysql-test/suite/jp/r/jp_subquery_utf8.result
share/mysql-test/suite/jp/r/jp_substring_sjis.result
share/mysql-test/suite/jp/r/jp_substring_ucs2.result
share/mysql-test/suite/jp/r/jp_substring_ujis.result
share/mysql-test/suite/jp/r/jp_substring_utf8.result
share/mysql-test/suite/jp/r/jp_trim_sjis.result
share/mysql-test/suite/jp/r/jp_trim_ucs2.result
share/mysql-test/suite/jp/r/jp_trim_ujis.result
share/mysql-test/suite/jp/r/jp_trim_utf8.result
share/mysql-test/suite/jp/r/jp_union_ujis.result
share/mysql-test/suite/jp/r/jp_update_sjis.result
share/mysql-test/suite/jp/r/jp_update_ucs2.result
share/mysql-test/suite/jp/r/jp_update_ujis.result
share/mysql-test/suite/jp/r/jp_update_utf8.result
share/mysql-test/suite/jp/r/jp_where_sjis.result
share/mysql-test/suite/jp/r/jp_where_ucs2.result
share/mysql-test/suite/jp/r/jp_where_ujis.result
share/mysql-test/suite/jp/r/jp_where_utf8.result
share/mysql-test/suite/jp/std_data/jisx0201_sjis.dat
share/mysql-test/suite/jp/std_data/jisx0201_ucs2.dat
share/mysql-test/suite/jp/std_data/jisx0201_ujis.dat
share/mysql-test/suite/jp/std_data/jisx0201_utf8.dat
share/mysql-test/suite/jp/std_data/jisx0208_sjis.dat
share/mysql-test/suite/jp/std_data/jisx0208_sjis2.dat
share/mysql-test/suite/jp/std_data/jisx0208_sjis3.dat
share/mysql-test/suite/jp/std_data/jisx0208_ucs2.dat
share/mysql-test/suite/jp/std_data/jisx0208_ujis.dat
share/mysql-test/suite/jp/std_data/jisx0208_utf8.dat
share/mysql-test/suite/jp/std_data/jisx0212_ucs2.dat
share/mysql-test/suite/jp/std_data/jisx0212_ujis.dat
share/mysql-test/suite/jp/std_data/jisx0212_utf8.dat
share/mysql-test/suite/jp/t/disabled.def
share/mysql-test/suite/jp/t/jp_alter_sjis.test
share/mysql-test/suite/jp/t/jp_alter_ucs2.test
share/mysql-test/suite/jp/t/jp_alter_ujis.test
share/mysql-test/suite/jp/t/jp_alter_utf8.test
share/mysql-test/suite/jp/t/jp_charlength_sjis.test
share/mysql-test/suite/jp/t/jp_charlength_ucs2.test
share/mysql-test/suite/jp/t/jp_charlength_ujis.test
share/mysql-test/suite/jp/t/jp_charlength_utf8.test
share/mysql-test/suite/jp/t/jp_charset_sjis.test
share/mysql-test/suite/jp/t/jp_charset_ucs2.test
share/mysql-test/suite/jp/t/jp_charset_ujis.test
share/mysql-test/suite/jp/t/jp_charset_utf8.test
share/mysql-test/suite/jp/t/jp_convert_sjis.test
share/mysql-test/suite/jp/t/jp_convert_ucs2.test
share/mysql-test/suite/jp/t/jp_convert_ujis.test
share/mysql-test/suite/jp/t/jp_convert_utf8.test
share/mysql-test/suite/jp/t/jp_create_db_sjis.test
share/mysql-test/suite/jp/t/jp_create_db_ucs2.test
share/mysql-test/suite/jp/t/jp_create_db_ujis.test
share/mysql-test/suite/jp/t/jp_create_db_utf8.test
share/mysql-test/suite/jp/t/jp_create_tbl_sjis.test
share/mysql-test/suite/jp/t/jp_create_tbl_ucs2.test
share/mysql-test/suite/jp/t/jp_create_tbl_ujis.test
share/mysql-test/suite/jp/t/jp_create_tbl_utf8.test
share/mysql-test/suite/jp/t/jp_enum_sjis-master.opt
share/mysql-test/suite/jp/t/jp_enum_sjis.test
share/mysql-test/suite/jp/t/jp_enum_ucs2-master.opt
share/mysql-test/suite/jp/t/jp_enum_ucs2.test
share/mysql-test/suite/jp/t/jp_enum_ujis-master.opt
share/mysql-test/suite/jp/t/jp_enum_ujis.test
share/mysql-test/suite/jp/t/jp_enum_utf8-master.opt
share/mysql-test/suite/jp/t/jp_enum_utf8.test
share/mysql-test/suite/jp/t/jp_insert_sjis.test
share/mysql-test/suite/jp/t/jp_insert_ucs2.test
share/mysql-test/suite/jp/t/jp_insert_ujis.test
share/mysql-test/suite/jp/t/jp_insert_utf8.test
share/mysql-test/suite/jp/t/jp_instr_sjis.test
share/mysql-test/suite/jp/t/jp_instr_ucs2.test
share/mysql-test/suite/jp/t/jp_instr_ujis.test
share/mysql-test/suite/jp/t/jp_instr_utf8.test
share/mysql-test/suite/jp/t/jp_join_sjis.test
share/mysql-test/suite/jp/t/jp_join_ucs2.test
share/mysql-test/suite/jp/t/jp_join_ujis.test
share/mysql-test/suite/jp/t/jp_join_utf8.test
share/mysql-test/suite/jp/t/jp_left_sjis.test
share/mysql-test/suite/jp/t/jp_left_ucs2.test
share/mysql-test/suite/jp/t/jp_left_ujis.test
share/mysql-test/suite/jp/t/jp_left_utf8.test
share/mysql-test/suite/jp/t/jp_length_sjis.test
share/mysql-test/suite/jp/t/jp_length_ucs2.test
share/mysql-test/suite/jp/t/jp_length_ujis.test
share/mysql-test/suite/jp/t/jp_length_utf8.test
share/mysql-test/suite/jp/t/jp_like_sjis.test
share/mysql-test/suite/jp/t/jp_like_ucs2.test
share/mysql-test/suite/jp/t/jp_like_ujis.test
share/mysql-test/suite/jp/t/jp_like_utf8.test
share/mysql-test/suite/jp/t/jp_locate_sjis.test
share/mysql-test/suite/jp/t/jp_locate_ucs2.test
share/mysql-test/suite/jp/t/jp_locate_ujis.test
share/mysql-test/suite/jp/t/jp_locate_utf8.test
share/mysql-test/suite/jp/t/jp_lpad_sjis.test
share/mysql-test/suite/jp/t/jp_lpad_ucs2.test
share/mysql-test/suite/jp/t/jp_lpad_ujis.test
share/mysql-test/suite/jp/t/jp_lpad_utf8.test
share/mysql-test/suite/jp/t/jp_ltrim_sjis.test
share/mysql-test/suite/jp/t/jp_ltrim_ucs2.test
share/mysql-test/suite/jp/t/jp_ltrim_ujis.test
share/mysql-test/suite/jp/t/jp_ltrim_utf8.test
share/mysql-test/suite/jp/t/jp_ps_sjis.test
share/mysql-test/suite/jp/t/jp_ps_ujis.test
share/mysql-test/suite/jp/t/jp_replace_sjis.test
share/mysql-test/suite/jp/t/jp_replace_ucs2.test
share/mysql-test/suite/jp/t/jp_replace_ujis.test
share/mysql-test/suite/jp/t/jp_replace_utf8.test
share/mysql-test/suite/jp/t/jp_reverse_sjis.test
share/mysql-test/suite/jp/t/jp_reverse_ucs2.test
share/mysql-test/suite/jp/t/jp_reverse_ujis.test
share/mysql-test/suite/jp/t/jp_reverse_utf8.test
share/mysql-test/suite/jp/t/jp_right_sjis.test
share/mysql-test/suite/jp/t/jp_right_ucs2.test
share/mysql-test/suite/jp/t/jp_right_ujis.test
share/mysql-test/suite/jp/t/jp_right_utf8.test
share/mysql-test/suite/jp/t/jp_rpad_sjis.test
share/mysql-test/suite/jp/t/jp_rpad_ucs2.test
share/mysql-test/suite/jp/t/jp_rpad_ujis.test
share/mysql-test/suite/jp/t/jp_rpad_utf8.test
share/mysql-test/suite/jp/t/jp_rtrim_sjis.test
share/mysql-test/suite/jp/t/jp_rtrim_ucs2.test
share/mysql-test/suite/jp/t/jp_rtrim_ujis.test
share/mysql-test/suite/jp/t/jp_rtrim_utf8.test
share/mysql-test/suite/jp/t/jp_select_sjis.test
share/mysql-test/suite/jp/t/jp_select_ucs2.test
share/mysql-test/suite/jp/t/jp_select_ujis.test
share/mysql-test/suite/jp/t/jp_select_utf8.test
share/mysql-test/suite/jp/t/jp_subquery_sjis.test
share/mysql-test/suite/jp/t/jp_subquery_ucs2.test
share/mysql-test/suite/jp/t/jp_subquery_ujis.test
share/mysql-test/suite/jp/t/jp_subquery_utf8.test
share/mysql-test/suite/jp/t/jp_substring_sjis.test
share/mysql-test/suite/jp/t/jp_substring_ucs2.test
share/mysql-test/suite/jp/t/jp_substring_ujis.test
share/mysql-test/suite/jp/t/jp_substring_utf8.test
share/mysql-test/suite/jp/t/jp_trim_sjis.test
share/mysql-test/suite/jp/t/jp_trim_ucs2.test
share/mysql-test/suite/jp/t/jp_trim_ujis.test
share/mysql-test/suite/jp/t/jp_trim_utf8.test
share/mysql-test/suite/jp/t/jp_union_ujis.test
share/mysql-test/suite/jp/t/jp_update_sjis.test
share/mysql-test/suite/jp/t/jp_update_ucs2.test
share/mysql-test/suite/jp/t/jp_update_ujis.test
share/mysql-test/suite/jp/t/jp_update_utf8.test
share/mysql-test/suite/jp/t/jp_where_sjis.test
share/mysql-test/suite/jp/t/jp_where_ucs2.test
share/mysql-test/suite/jp/t/jp_where_ujis.test
share/mysql-test/suite/jp/t/jp_where_utf8.test
share/mysql-test/suite/manual/r/rpl_replication_delay.result
share/mysql-test/suite/manual/t/rpl_replication_delay-slave.opt
share/mysql-test/suite/manual/t/rpl_replication_delay.test
share/mysql-test/suite/ndb/my.cnf
share/mysql-test/suite/ndb/r/loaddata_autocom_ndb.result
share/mysql-test/suite/ndb/r/ndb_alter_table.result
share/mysql-test/suite/ndb/r/ndb_alter_table2.result
share/mysql-test/suite/ndb/r/ndb_alter_table3.result
share/mysql-test/suite/ndb/r/ndb_auto_increment.result
share/mysql-test/suite/ndb/r/ndb_autoinc.result
share/mysql-test/suite/ndb/r/ndb_basic.result
share/mysql-test/suite/ndb/r/ndb_binlog_basic.result
share/mysql-test/suite/ndb/r/ndb_binlog_ddl_multi.result
share/mysql-test/suite/ndb/r/ndb_binlog_discover.result
share/mysql-test/suite/ndb/r/ndb_binlog_format.result
share/mysql-test/suite/ndb/r/ndb_binlog_ignore_db.result
share/mysql-test/suite/ndb/r/ndb_binlog_log_bin.result
share/mysql-test/suite/ndb/r/ndb_binlog_multi.result
share/mysql-test/suite/ndb/r/ndb_bitfield.result
share/mysql-test/suite/ndb/r/ndb_blob.result
share/mysql-test/suite/ndb/r/ndb_blob_partition.result
share/mysql-test/suite/ndb/r/ndb_bug26793.result
share/mysql-test/suite/ndb/r/ndb_bug31477.result
share/mysql-test/suite/ndb/r/ndb_cache.result
share/mysql-test/suite/ndb/r/ndb_cache2.result
share/mysql-test/suite/ndb/r/ndb_cache_multi.result
share/mysql-test/suite/ndb/r/ndb_cache_multi2.result
share/mysql-test/suite/ndb/r/ndb_charset.result
share/mysql-test/suite/ndb/r/ndb_condition_pushdown.result
share/mysql-test/suite/ndb/r/ndb_config.result
share/mysql-test/suite/ndb/r/ndb_config2.result
share/mysql-test/suite/ndb/r/ndb_cursor.result
share/mysql-test/suite/ndb/r/ndb_database.result
share/mysql-test/suite/ndb/r/ndb_dd_alter.result
share/mysql-test/suite/ndb/r/ndb_dd_basic.result
share/mysql-test/suite/ndb/r/ndb_dd_ddl.result
share/mysql-test/suite/ndb/r/ndb_dd_disk2memory.result
share/mysql-test/suite/ndb/r/ndb_dd_dump.result
share/mysql-test/suite/ndb/r/ndb_dd_sql_features.result
share/mysql-test/suite/ndb/r/ndb_gis.result
share/mysql-test/suite/ndb/r/ndb_grant.result
share/mysql-test/suite/ndb/r/ndb_index.result
share/mysql-test/suite/ndb/r/ndb_index_ordered.result
share/mysql-test/suite/ndb/r/ndb_index_unique.result
share/mysql-test/suite/ndb/r/ndb_insert.result
share/mysql-test/suite/ndb/r/ndb_limit.result
share/mysql-test/suite/ndb/r/ndb_load.result
share/mysql-test/suite/ndb/r/ndb_loaddatalocal.result
share/mysql-test/suite/ndb/r/ndb_lock.result
share/mysql-test/suite/ndb/r/ndb_lock_table.result
share/mysql-test/suite/ndb/r/ndb_minmax.result
share/mysql-test/suite/ndb/r/ndb_multi.result
share/mysql-test/suite/ndb/r/ndb_multi_row.result
share/mysql-test/suite/ndb/r/ndb_partition_error.result
share/mysql-test/suite/ndb/r/ndb_partition_error2.result
share/mysql-test/suite/ndb/r/ndb_partition_key.result
share/mysql-test/suite/ndb/r/ndb_partition_list.result
share/mysql-test/suite/ndb/r/ndb_partition_range.result
share/mysql-test/suite/ndb/r/ndb_read_multi_range.result
share/mysql-test/suite/ndb/r/ndb_rename.result
share/mysql-test/suite/ndb/r/ndb_replace.result
share/mysql-test/suite/ndb/r/ndb_restore.result
share/mysql-test/suite/ndb/r/ndb_restore_compat.result
share/mysql-test/suite/ndb/r/ndb_restore_different_endian_data.result
share/mysql-test/suite/ndb/r/ndb_restore_partition.result
share/mysql-test/suite/ndb/r/ndb_restore_print.result
share/mysql-test/suite/ndb/r/ndb_row_format.result
share/mysql-test/suite/ndb/r/ndb_single_user.result
share/mysql-test/suite/ndb/r/ndb_sp.result
share/mysql-test/suite/ndb/r/ndb_subquery.result
share/mysql-test/suite/ndb/r/ndb_temporary.result
share/mysql-test/suite/ndb/r/ndb_tmp_table_and_DDL.result
share/mysql-test/suite/ndb/r/ndb_transaction.result
share/mysql-test/suite/ndb/r/ndb_trigger.result
share/mysql-test/suite/ndb/r/ndb_truncate.result
share/mysql-test/suite/ndb/r/ndb_types.result
share/mysql-test/suite/ndb/r/ndb_update.result
share/mysql-test/suite/ndb/r/ndb_update_no_read.result
share/mysql-test/suite/ndb/r/ndb_view.result
share/mysql-test/suite/ndb/r/ndbapi.result
share/mysql-test/suite/ndb/r/ps_7ndb.result
share/mysql-test/suite/ndb/r/strict_autoinc_5ndb.result
share/mysql-test/suite/ndb/t/disabled.def
share/mysql-test/suite/ndb/t/loaddata_autocom_ndb.test
share/mysql-test/suite/ndb/t/ndb_alter_table.test
share/mysql-test/suite/ndb/t/ndb_alter_table2.test
share/mysql-test/suite/ndb/t/ndb_alter_table3.test
share/mysql-test/suite/ndb/t/ndb_auto_increment.test
share/mysql-test/suite/ndb/t/ndb_autoinc.test
share/mysql-test/suite/ndb/t/ndb_basic.test
share/mysql-test/suite/ndb/t/ndb_binlog_basic.test
share/mysql-test/suite/ndb/t/ndb_binlog_ddl_multi.test
share/mysql-test/suite/ndb/t/ndb_binlog_discover.test
share/mysql-test/suite/ndb/t/ndb_binlog_format.test
share/mysql-test/suite/ndb/t/ndb_binlog_ignore_db-master.opt
share/mysql-test/suite/ndb/t/ndb_binlog_ignore_db.test
share/mysql-test/suite/ndb/t/ndb_binlog_log_bin.test
share/mysql-test/suite/ndb/t/ndb_binlog_multi.test
share/mysql-test/suite/ndb/t/ndb_bitfield.test
share/mysql-test/suite/ndb/t/ndb_blob.test
share/mysql-test/suite/ndb/t/ndb_blob_partition.test
share/mysql-test/suite/ndb/t/ndb_bug26793.test
share/mysql-test/suite/ndb/t/ndb_bug31477.test
share/mysql-test/suite/ndb/t/ndb_cache.test
share/mysql-test/suite/ndb/t/ndb_cache2.test
share/mysql-test/suite/ndb/t/ndb_cache_multi.test
share/mysql-test/suite/ndb/t/ndb_cache_multi2.test
share/mysql-test/suite/ndb/t/ndb_charset.test
share/mysql-test/suite/ndb/t/ndb_condition_pushdown.test
share/mysql-test/suite/ndb/t/ndb_config.test
share/mysql-test/suite/ndb/t/ndb_config2.test
share/mysql-test/suite/ndb/t/ndb_cursor.test
share/mysql-test/suite/ndb/t/ndb_database.test
share/mysql-test/suite/ndb/t/ndb_dd_alter.test
share/mysql-test/suite/ndb/t/ndb_dd_basic.test
share/mysql-test/suite/ndb/t/ndb_dd_ddl.test
share/mysql-test/suite/ndb/t/ndb_dd_disk2memory.test
share/mysql-test/suite/ndb/t/ndb_dd_dump.test
share/mysql-test/suite/ndb/t/ndb_dd_sql_features.test
share/mysql-test/suite/ndb/t/ndb_gis.test
share/mysql-test/suite/ndb/t/ndb_grant.later
share/mysql-test/suite/ndb/t/ndb_index.test
share/mysql-test/suite/ndb/t/ndb_index_ordered.test
share/mysql-test/suite/ndb/t/ndb_index_unique.test
share/mysql-test/suite/ndb/t/ndb_insert.test
share/mysql-test/suite/ndb/t/ndb_limit.test
share/mysql-test/suite/ndb/t/ndb_load.test
share/mysql-test/suite/ndb/t/ndb_loaddatalocal.test
share/mysql-test/suite/ndb/t/ndb_lock.test
share/mysql-test/suite/ndb/t/ndb_lock_table.test
share/mysql-test/suite/ndb/t/ndb_minmax.test
share/mysql-test/suite/ndb/t/ndb_multi.test
share/mysql-test/suite/ndb/t/ndb_multi_row.test
share/mysql-test/suite/ndb/t/ndb_partition_error.test
share/mysql-test/suite/ndb/t/ndb_partition_error2-master.opt
share/mysql-test/suite/ndb/t/ndb_partition_error2.test
share/mysql-test/suite/ndb/t/ndb_partition_key.test
share/mysql-test/suite/ndb/t/ndb_partition_list.test
share/mysql-test/suite/ndb/t/ndb_partition_range.test
share/mysql-test/suite/ndb/t/ndb_read_multi_range.test
share/mysql-test/suite/ndb/t/ndb_rename.test
share/mysql-test/suite/ndb/t/ndb_replace.test
share/mysql-test/suite/ndb/t/ndb_restore.test
share/mysql-test/suite/ndb/t/ndb_restore_compat.test
share/mysql-test/suite/ndb/t/ndb_restore_different_endian_data.test
share/mysql-test/suite/ndb/t/ndb_restore_partition-master.opt
share/mysql-test/suite/ndb/t/ndb_restore_partition.test
share/mysql-test/suite/ndb/t/ndb_restore_print.test
share/mysql-test/suite/ndb/t/ndb_row_format.test
share/mysql-test/suite/ndb/t/ndb_single_user.test
share/mysql-test/suite/ndb/t/ndb_sp.test
share/mysql-test/suite/ndb/t/ndb_subquery.test
share/mysql-test/suite/ndb/t/ndb_temporary.test
share/mysql-test/suite/ndb/t/ndb_tmp_table_and_DDL.test
share/mysql-test/suite/ndb/t/ndb_transaction.test
share/mysql-test/suite/ndb/t/ndb_trigger.test
share/mysql-test/suite/ndb/t/ndb_truncate.test
share/mysql-test/suite/ndb/t/ndb_types.test
share/mysql-test/suite/ndb/t/ndb_update.test
share/mysql-test/suite/ndb/t/ndb_update_no_read.test
share/mysql-test/suite/ndb/t/ndb_view.test
share/mysql-test/suite/ndb/t/ndbapi.test
share/mysql-test/suite/ndb/t/ps_7ndb.test
share/mysql-test/suite/ndb/t/strict_autoinc_5ndb.test
share/mysql-test/suite/ndb_team/r/ndb_autodiscover.result
share/mysql-test/suite/ndb_team/r/ndb_autodiscover2.result
share/mysql-test/suite/ndb_team/r/ndb_autodiscover3.result
share/mysql-test/suite/ndb_team/r/ndb_backup_print.result
share/mysql-test/suite/ndb_team/r/ndb_dd_backuprestore.result
share/mysql-test/suite/ndb_team/r/rpl_ndb_dd_advance.result
share/mysql-test/suite/ndb_team/r/rpl_ndb_extraColMaster.result
share/mysql-test/suite/ndb_team/r/rpl_ndb_mix_innodb.result
share/mysql-test/suite/ndb_team/t/disabled.def
share/mysql-test/suite/ndb_team/t/ndb_autodiscover.test
share/mysql-test/suite/ndb_team/t/ndb_autodiscover2-master.opt
share/mysql-test/suite/ndb_team/t/ndb_autodiscover2.test
share/mysql-test/suite/ndb_team/t/ndb_autodiscover3.test
share/mysql-test/suite/ndb_team/t/ndb_backup_print.test
share/mysql-test/suite/ndb_team/t/ndb_dd_backuprestore.test
share/mysql-test/suite/ndb_team/t/rpl_ndb_dd_advance.test
share/mysql-test/suite/ndb_team/t/rpl_ndb_extraColMaster.test
share/mysql-test/suite/ndb_team/t/rpl_ndb_mix_innodb-master.opt
share/mysql-test/suite/ndb_team/t/rpl_ndb_mix_innodb.test
share/mysql-test/suite/parts/inc/methods1.inc
share/mysql-test/suite/parts/inc/part_blocked_sql_funcs_main.inc
share/mysql-test/suite/parts/inc/part_supported_sql_funcs_delete.inc
share/mysql-test/suite/parts/inc/part_supported_sql_funcs_main.inc
share/mysql-test/suite/parts/inc/partition.pre
share/mysql-test/suite/parts/inc/partition_10.inc
share/mysql-test/suite/parts/inc/partition_11.inc
share/mysql-test/suite/parts/inc/partition_12.inc
share/mysql-test/suite/parts/inc/partition_20.inc
share/mysql-test/suite/parts/inc/partition_alter1_1.inc
share/mysql-test/suite/parts/inc/partition_alter1_1_2.inc
share/mysql-test/suite/parts/inc/partition_alter1_2.inc
share/mysql-test/suite/parts/inc/partition_alter2_1.inc
share/mysql-test/suite/parts/inc/partition_alter2_2.inc
share/mysql-test/suite/parts/inc/partition_alter3.inc
share/mysql-test/suite/parts/inc/partition_alter4.inc
share/mysql-test/suite/parts/inc/partition_alter_1.inc
share/mysql-test/suite/parts/inc/partition_alter_11.inc
share/mysql-test/suite/parts/inc/partition_alter_13.inc
share/mysql-test/suite/parts/inc/partition_alter_41.inc
share/mysql-test/suite/parts/inc/partition_auto_increment.inc
share/mysql-test/suite/parts/inc/partition_basic.inc
share/mysql-test/suite/parts/inc/partition_basic_symlink.inc
share/mysql-test/suite/parts/inc/partition_bigint.inc
share/mysql-test/suite/parts/inc/partition_binary.inc
share/mysql-test/suite/parts/inc/partition_bit.inc
share/mysql-test/suite/parts/inc/partition_blob.inc
share/mysql-test/suite/parts/inc/partition_blocked_sql_funcs.inc
share/mysql-test/suite/parts/inc/partition_char.inc
share/mysql-test/suite/parts/inc/partition_check.inc
share/mysql-test/suite/parts/inc/partition_check_drop.inc
share/mysql-test/suite/parts/inc/partition_check_read.inc
share/mysql-test/suite/parts/inc/partition_check_read1.inc
share/mysql-test/suite/parts/inc/partition_check_read2.inc
share/mysql-test/suite/parts/inc/partition_cleanup.inc
share/mysql-test/suite/parts/inc/partition_date.inc
share/mysql-test/suite/parts/inc/partition_datetime.inc
share/mysql-test/suite/parts/inc/partition_decimal.inc
share/mysql-test/suite/parts/inc/partition_directory.inc
share/mysql-test/suite/parts/inc/partition_double.inc
share/mysql-test/suite/parts/inc/partition_engine.inc
share/mysql-test/suite/parts/inc/partition_enum.inc
share/mysql-test/suite/parts/inc/partition_float.inc
share/mysql-test/suite/parts/inc/partition_int.inc
share/mysql-test/suite/parts/inc/partition_key_16col.inc
share/mysql-test/suite/parts/inc/partition_key_32col.inc
share/mysql-test/suite/parts/inc/partition_key_4col.inc
share/mysql-test/suite/parts/inc/partition_key_8col.inc
share/mysql-test/suite/parts/inc/partition_layout.inc
share/mysql-test/suite/parts/inc/partition_layout_check1.inc
share/mysql-test/suite/parts/inc/partition_layout_check2.inc
share/mysql-test/suite/parts/inc/partition_mediumint.inc
share/mysql-test/suite/parts/inc/partition_methods1.inc
share/mysql-test/suite/parts/inc/partition_methods2.inc
share/mysql-test/suite/parts/inc/partition_mgm.inc
share/mysql-test/suite/parts/inc/partition_set.inc
share/mysql-test/suite/parts/inc/partition_smallint.inc
share/mysql-test/suite/parts/inc/partition_supported_sql_funcs.inc
share/mysql-test/suite/parts/inc/partition_syntax.inc
share/mysql-test/suite/parts/inc/partition_syntax_1.inc
share/mysql-test/suite/parts/inc/partition_syntax_2.inc
share/mysql-test/suite/parts/inc/partition_text.inc
share/mysql-test/suite/parts/inc/partition_time.inc
share/mysql-test/suite/parts/inc/partition_timestamp.inc
share/mysql-test/suite/parts/inc/partition_tinyint.inc
share/mysql-test/suite/parts/inc/partition_trigg1.inc
share/mysql-test/suite/parts/inc/partition_trigg2.inc
share/mysql-test/suite/parts/inc/partition_trigg3.inc
share/mysql-test/suite/parts/inc/partition_value.inc
share/mysql-test/suite/parts/inc/partition_varbinary.inc
share/mysql-test/suite/parts/inc/partition_varchar.inc
share/mysql-test/suite/parts/inc/partition_year.inc
share/mysql-test/suite/parts/r/ndb_dd_backuprestore.result
share/mysql-test/suite/parts/r/part_blocked_sql_func_innodb.result
share/mysql-test/suite/parts/r/part_blocked_sql_func_myisam.result
share/mysql-test/suite/parts/r/part_supported_sql_func_innodb.result
share/mysql-test/suite/parts/r/part_supported_sql_func_myisam.result
share/mysql-test/suite/parts/r/part_supported_sql_func_ndb.result
share/mysql-test/suite/parts/r/partition_alter1_1_2_innodb.result
share/mysql-test/suite/parts/r/partition_alter1_1_2_myisam.result
share/mysql-test/suite/parts/r/partition_alter1_1_2_ndb.result
share/mysql-test/suite/parts/r/partition_alter1_1_innodb.result
share/mysql-test/suite/parts/r/partition_alter1_1_myisam.result
share/mysql-test/suite/parts/r/partition_alter1_1_ndb.result
share/mysql-test/suite/parts/r/partition_alter1_2_innodb.result
share/mysql-test/suite/parts/r/partition_alter1_2_myisam.result
share/mysql-test/suite/parts/r/partition_alter1_2_ndb.result
share/mysql-test/suite/parts/r/partition_alter2_1_innodb.result
share/mysql-test/suite/parts/r/partition_alter2_1_myisam.result
share/mysql-test/suite/parts/r/partition_alter2_2_innodb.result
share/mysql-test/suite/parts/r/partition_alter2_2_myisam.result
share/mysql-test/suite/parts/r/partition_alter3_innodb.result
share/mysql-test/suite/parts/r/partition_alter3_myisam.result
share/mysql-test/suite/parts/r/partition_alter4_innodb.result
share/mysql-test/suite/parts/r/partition_alter4_myisam.result
share/mysql-test/suite/parts/r/partition_auto_increment_archive.result
share/mysql-test/suite/parts/r/partition_auto_increment_blackhole.result
share/mysql-test/suite/parts/r/partition_auto_increment_innodb.result
share/mysql-test/suite/parts/r/partition_auto_increment_memory.result
share/mysql-test/suite/parts/r/partition_auto_increment_myisam.result
share/mysql-test/suite/parts/r/partition_auto_increment_ndb.result
share/mysql-test/suite/parts/r/partition_basic_innodb.result
share/mysql-test/suite/parts/r/partition_basic_myisam.result
share/mysql-test/suite/parts/r/partition_basic_symlink_innodb.result
share/mysql-test/suite/parts/r/partition_basic_symlink_myisam.result
share/mysql-test/suite/parts/r/partition_bit_innodb.result
share/mysql-test/suite/parts/r/partition_bit_myisam.result
share/mysql-test/suite/parts/r/partition_char_innodb.result
share/mysql-test/suite/parts/r/partition_char_myisam.result
share/mysql-test/suite/parts/r/partition_datetime_innodb.result
share/mysql-test/suite/parts/r/partition_datetime_myisam.result
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/suite/parts/r/partition_debug_sync_innodb.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/parts/r/partition_decimal_innodb.result
share/mysql-test/suite/parts/r/partition_decimal_myisam.result
share/mysql-test/suite/parts/r/partition_engine_innodb.result
share/mysql-test/suite/parts/r/partition_engine_myisam.result
share/mysql-test/suite/parts/r/partition_engine_ndb.result
share/mysql-test/suite/parts/r/partition_float_innodb.result
share/mysql-test/suite/parts/r/partition_float_myisam.result
share/mysql-test/suite/parts/r/partition_int_innodb.result
share/mysql-test/suite/parts/r/partition_int_myisam.result
share/mysql-test/suite/parts/r/partition_int_ndb.result
share/mysql-test/suite/parts/r/partition_mgm_lc0_archive.result
share/mysql-test/suite/parts/r/partition_mgm_lc0_innodb.result
share/mysql-test/suite/parts/r/partition_mgm_lc0_memory.result
share/mysql-test/suite/parts/r/partition_mgm_lc0_myisam.result
share/mysql-test/suite/parts/r/partition_mgm_lc0_ndb.result
share/mysql-test/suite/parts/r/partition_mgm_lc1_archive.result
share/mysql-test/suite/parts/r/partition_mgm_lc1_innodb.result
share/mysql-test/suite/parts/r/partition_mgm_lc1_memory.result
share/mysql-test/suite/parts/r/partition_mgm_lc1_myisam.result
share/mysql-test/suite/parts/r/partition_mgm_lc1_ndb.result
share/mysql-test/suite/parts/r/partition_mgm_lc2_archive.result
share/mysql-test/suite/parts/r/partition_mgm_lc2_innodb.result
share/mysql-test/suite/parts/r/partition_mgm_lc2_memory.result
share/mysql-test/suite/parts/r/partition_mgm_lc2_myisam.result
share/mysql-test/suite/parts/r/partition_mgm_lc2_ndb.result
share/mysql-test/suite/parts/r/partition_recover_myisam.result
share/mysql-test/suite/parts/r/partition_repair_myisam.result
share/mysql-test/suite/parts/r/partition_special_innodb.result
share/mysql-test/suite/parts/r/partition_special_myisam.result
share/mysql-test/suite/parts/r/partition_syntax_innodb.result
share/mysql-test/suite/parts/r/partition_syntax_myisam.result
share/mysql-test/suite/parts/r/partition_syntax_ndb.result
share/mysql-test/suite/parts/r/partition_t55.out
share/mysql-test/suite/parts/r/partition_value_innodb.result
share/mysql-test/suite/parts/r/partition_value_myisam.result
share/mysql-test/suite/parts/r/partition_value_ndb.result
share/mysql-test/suite/parts/r/rpl_partition.result
share/mysql-test/suite/parts/t/disabled.def
share/mysql-test/suite/parts/t/ndb_dd_backuprestore.test
share/mysql-test/suite/parts/t/part_blocked_sql_func_innodb.test
share/mysql-test/suite/parts/t/part_blocked_sql_func_myisam.test
share/mysql-test/suite/parts/t/part_supported_sql_func_innodb.test
share/mysql-test/suite/parts/t/part_supported_sql_func_myisam.test
share/mysql-test/suite/parts/t/part_supported_sql_func_ndb.test
share/mysql-test/suite/parts/t/partition_alter1_1_2_innodb.test
share/mysql-test/suite/parts/t/partition_alter1_1_2_myisam.test
share/mysql-test/suite/parts/t/partition_alter1_1_2_ndb.test
share/mysql-test/suite/parts/t/partition_alter1_1_innodb.test
share/mysql-test/suite/parts/t/partition_alter1_1_myisam.test
share/mysql-test/suite/parts/t/partition_alter1_1_ndb.test
share/mysql-test/suite/parts/t/partition_alter1_2_innodb.test
share/mysql-test/suite/parts/t/partition_alter1_2_myisam.test
share/mysql-test/suite/parts/t/partition_alter1_2_ndb.test
share/mysql-test/suite/parts/t/partition_alter2_1_innodb.test
share/mysql-test/suite/parts/t/partition_alter2_1_myisam.test
share/mysql-test/suite/parts/t/partition_alter2_2_innodb.test
share/mysql-test/suite/parts/t/partition_alter2_2_myisam.test
share/mysql-test/suite/parts/t/partition_alter3_innodb.test
share/mysql-test/suite/parts/t/partition_alter3_myisam.test
share/mysql-test/suite/parts/t/partition_alter4_innodb.test
share/mysql-test/suite/parts/t/partition_alter4_myisam.test
share/mysql-test/suite/parts/t/partition_auto_increment_archive.test
share/mysql-test/suite/parts/t/partition_auto_increment_blackhole.test
share/mysql-test/suite/parts/t/partition_auto_increment_innodb.test
share/mysql-test/suite/parts/t/partition_auto_increment_memory.test
share/mysql-test/suite/parts/t/partition_auto_increment_myisam.test
share/mysql-test/suite/parts/t/partition_auto_increment_ndb.test
share/mysql-test/suite/parts/t/partition_basic_innodb.test
share/mysql-test/suite/parts/t/partition_basic_myisam.test
share/mysql-test/suite/parts/t/partition_basic_ndb.test
share/mysql-test/suite/parts/t/partition_basic_symlink_innodb.test
share/mysql-test/suite/parts/t/partition_basic_symlink_myisam.test
share/mysql-test/suite/parts/t/partition_bit_innodb.test
share/mysql-test/suite/parts/t/partition_bit_myisam.test
share/mysql-test/suite/parts/t/partition_char_innodb.test
share/mysql-test/suite/parts/t/partition_char_myisam.test
share/mysql-test/suite/parts/t/partition_datetime_innodb.test
share/mysql-test/suite/parts/t/partition_datetime_myisam.test
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/suite/parts/t/partition_debug_sync_innodb-master.opt
share/mysql-test/suite/parts/t/partition_debug_sync_innodb.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/parts/t/partition_decimal_innodb.test
share/mysql-test/suite/parts/t/partition_decimal_myisam.test
share/mysql-test/suite/parts/t/partition_engine_innodb.test
share/mysql-test/suite/parts/t/partition_engine_myisam.test
share/mysql-test/suite/parts/t/partition_engine_ndb.test
share/mysql-test/suite/parts/t/partition_float_innodb.test
share/mysql-test/suite/parts/t/partition_float_myisam.test
share/mysql-test/suite/parts/t/partition_int_innodb.test
share/mysql-test/suite/parts/t/partition_int_myisam.test
share/mysql-test/suite/parts/t/partition_int_ndb.test
share/mysql-test/suite/parts/t/partition_mgm_lc0_archive.test
share/mysql-test/suite/parts/t/partition_mgm_lc0_innodb.test
share/mysql-test/suite/parts/t/partition_mgm_lc0_memory.test
share/mysql-test/suite/parts/t/partition_mgm_lc0_myisam.test
share/mysql-test/suite/parts/t/partition_mgm_lc0_ndb.test
share/mysql-test/suite/parts/t/partition_mgm_lc1_archive-master.opt
share/mysql-test/suite/parts/t/partition_mgm_lc1_archive.test
share/mysql-test/suite/parts/t/partition_mgm_lc1_innodb-master.opt
share/mysql-test/suite/parts/t/partition_mgm_lc1_innodb.test
share/mysql-test/suite/parts/t/partition_mgm_lc1_memory-master.opt
share/mysql-test/suite/parts/t/partition_mgm_lc1_memory.test
share/mysql-test/suite/parts/t/partition_mgm_lc1_myisam-master.opt
share/mysql-test/suite/parts/t/partition_mgm_lc1_myisam.test
share/mysql-test/suite/parts/t/partition_mgm_lc1_ndb-master.opt
share/mysql-test/suite/parts/t/partition_mgm_lc1_ndb.test
share/mysql-test/suite/parts/t/partition_mgm_lc2_archive-master.opt
share/mysql-test/suite/parts/t/partition_mgm_lc2_archive.test
share/mysql-test/suite/parts/t/partition_mgm_lc2_innodb-master.opt
share/mysql-test/suite/parts/t/partition_mgm_lc2_innodb.test
share/mysql-test/suite/parts/t/partition_mgm_lc2_memory-master.opt
share/mysql-test/suite/parts/t/partition_mgm_lc2_memory.test
share/mysql-test/suite/parts/t/partition_mgm_lc2_myisam-master.opt
share/mysql-test/suite/parts/t/partition_mgm_lc2_myisam.test
share/mysql-test/suite/parts/t/partition_mgm_lc2_ndb-master.opt
share/mysql-test/suite/parts/t/partition_mgm_lc2_ndb.test
share/mysql-test/suite/parts/t/partition_recover_myisam-master.opt
share/mysql-test/suite/parts/t/partition_recover_myisam.test
share/mysql-test/suite/parts/t/partition_repair_myisam.test
share/mysql-test/suite/parts/t/partition_special_innodb-master.opt
share/mysql-test/suite/parts/t/partition_special_innodb.test
share/mysql-test/suite/parts/t/partition_special_myisam.test
share/mysql-test/suite/parts/t/partition_syntax_innodb.test
share/mysql-test/suite/parts/t/partition_syntax_myisam.test
share/mysql-test/suite/parts/t/partition_syntax_ndb.test
share/mysql-test/suite/parts/t/partition_value_innodb.test
share/mysql-test/suite/parts/t/partition_value_myisam.test
share/mysql-test/suite/parts/t/partition_value_ndb.test
share/mysql-test/suite/parts/t/rpl_partition.test
share/mysql-test/suite/rpl/README
share/mysql-test/suite/rpl/combinations
share/mysql-test/suite/rpl/include/rpl_mixed_check_db.inc
share/mysql-test/suite/rpl/include/rpl_mixed_check_event.inc
share/mysql-test/suite/rpl/include/rpl_mixed_check_select.inc
share/mysql-test/suite/rpl/include/rpl_mixed_check_table.inc
share/mysql-test/suite/rpl/include/rpl_mixed_check_user.inc
share/mysql-test/suite/rpl/include/rpl_mixed_check_view.inc
share/mysql-test/suite/rpl/include/rpl_mixed_clear_tables.inc
share/mysql-test/suite/rpl/include/rpl_mixed_ddl.inc
share/mysql-test/suite/rpl/include/rpl_mixed_dml.inc
share/mysql-test/suite/rpl/include/rpl_mixed_show_binlog_format.inc
share/mysql-test/suite/rpl/my.cnf
share/mysql-test/suite/rpl/r/rpl000001.a.result
share/mysql-test/suite/rpl/r/rpl000001.b.result
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/rpl/r/rpl_000010.result
share/mysql-test/suite/rpl/r/rpl_000011.result
share/mysql-test/suite/rpl/r/rpl_000013.result
share/mysql-test/suite/rpl/r/rpl_000017.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_EE_err.result
share/mysql-test/suite/rpl/r/rpl_LD_INFILE.result
share/mysql-test/suite/rpl/r/rpl_alter.result
share/mysql-test/suite/rpl/r/rpl_alter_db.result
share/mysql-test/suite/rpl/r/rpl_auto_increment.result
share/mysql-test/suite/rpl/r/rpl_auto_increment_11932.result
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/rpl/r/rpl_auto_increment_bug33029.result
Update mysql51 to 5.1.65. While here, let to use OpenSSL instead of internal yaSSL with ssl option, may related to PR 46912. Changes in MySQL 5.1.65 (2012-08-09) Functionality Added or Changed * Important Change: The YEAR(2) data type is now deprecated because it is problematic. Support for YEAR(2) will be removed in a future release of MySQL. For more information, see Section 11.3.4, "YEAR(2) Limitations and Migrating to YEAR(4)". Bugs Fixed * The server did not build with gcc 4.7. (Bug #14238406) Changes in MySQL 5.1.64 (Not released) Functionality Added or Changed * Important Change: Replication: The SHOW BINARY LOGS statement (and its equivalent SHOW MASTER LOGS) may now be executed by a user with the REPLICATION CLIENT privilege. (Formerly, the SUPER privilege was necessary to use either form of this statement.)
2012-09-15 16:48:57 +02:00
share/mysql-test/suite/rpl/r/rpl_auto_increment_bug45679.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_auto_increment_update_failure.result
share/mysql-test/suite/rpl/r/rpl_begin_commit_rollback.result
share/mysql-test/suite/rpl/r/rpl_binlog_corruption.result
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/rpl/r/rpl_binlog_errors.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_binlog_grant.result
share/mysql-test/suite/rpl/r/rpl_binlog_max_cache_size.result
share/mysql-test/suite/rpl/r/rpl_bit.result
share/mysql-test/suite/rpl/r/rpl_bit_npk.result
share/mysql-test/suite/rpl/r/rpl_blackhole.result
share/mysql-test/suite/rpl/r/rpl_bug26395.result
share/mysql-test/suite/rpl/r/rpl_bug31076.result
share/mysql-test/suite/rpl/r/rpl_bug33931.result
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/suite/rpl/r/rpl_bug37426.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_bug38694.result
share/mysql-test/suite/rpl/r/rpl_change_master.result
share/mysql-test/suite/rpl/r/rpl_charset.result
share/mysql-test/suite/rpl/r/rpl_charset_sjis.result
share/mysql-test/suite/rpl/r/rpl_circular_for_4_hosts.result
share/mysql-test/suite/rpl/r/rpl_colSize.result
share/mysql-test/suite/rpl/r/rpl_commit_after_flush.result
share/mysql-test/suite/rpl/r/rpl_concurrency_error.result
Update mysql51-{client,server} to 5.1.50. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-50.html for full changes . InnoDB Notes: InnoDB Plugin has been upgraded to version 1.0.11. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), generic Linux RPM packages, and any builds produced with the icc compiler. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: Important Change: Replication: The LOAD DATA INFILE statement is now considered unsafe for statement-based replication. When using statement-based logging mode, the statement now produces a warning; when using mixed-format logging, the statement is made using the row-based format. (Bug#34283) Partitioning: UPDATE and INSERT statements affecting partitioned tables performed poorly when using row-based replication. (Bug#52517) Partitioning: INSERT ON DUPLICATE KEY UPDATE statements performed poorly on tables having many partitions. This was because the handler function for reading a row from a specific index was not optimized in the partitioning handler. (Bug#52455) The server could crash on shutdown, if started with --innodb-use-system-malloc=0. (Bug#55581) GROUP BY operations used max_sort_length inconsistently. (Bug#55188) Building MySQL on Solaris 8 x86 failed when using Sun Studio due to gcc inline assembler code. (Bug#55061) In debug builds, an assertion could be raised when the server tried to send an OK packet to the client after having failed to detect errors during processing of the WHERE condition of an UPDATE statement. (Bug#54734) The database server could crash when renaming a table that had active transactions. (This issue only affected the database server when built for debugging.) (Bug#54453) The server could crash during the recovery phase of startup, if it previously crashed while inserting BLOB or other large columns that use off-page storage into an InnoDB table created with ROW_FORMAT=REDUNDANT or ROW_FORMAT=COMPACT. (Bug#54408) For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#54358) A client could supply data in chunks to a prepared statement parameter other than of type TEXT or BLOB using the mysql_stmt_send_long_data() C API function (or COM_STMT_SEND_LONG_DATA command). This led to a crash because other data types are not valid for long data. (Bug#54041) mysql_secure_installation did not properly identify local accounts and could incorrectly remove nonlocal root accounts. (Bug#54004) Transactions could be incorrectly committed during recovery, rather than rolled back, if the server crashed and was restarted after performing ALTER TABLE...ADD PRIMARY KEY on an InnoDB table, or some other operation that involves copying the entire table. (Bug#53756) Portability problems in SHOW STATUS could lead to incorrect results on some platforms. (Bug#53493) Builds of MySQL generated a large number of warnings. (Bug#53445) With lower_case_table_names set to a nonzero value, searches for table or database names in INFORMATION_SCHEMA tables could produce incorrect results. (Bug#53095) The ABI check for MySQL failed to compile with gcc 4.5. (Bug#52514) mysql_secure_installation sometimes failed to locate the mysql client. (Bug#52274) Reading a ucs2 data file with LOAD DATA INFILE was subject to three problems. 1) Incorrect parsing of the file as ucs2 data, resulting in incorrect length of the parsed string. This is fixed by truncating the invalid trailing bytes (incomplete multibyte characters) when reading from the file. 2) Reads from a proper ucs2 file did not recognize newline characters. This is fixed by first checking whether a byte is a newline (or any other special character) before reading it as a part of a multibyte character. 3) When using user variables to hold column data, the character set of the user variable was set incorrectly to the database charset. This is fixed by setting it to the character set specified in the LOAD DATA INFILE statement, if any. (Bug#51876) Searches in INFORMATION_SCHEMA tables for rows matching a nonexistent database produced an error instead of an empty query result. (Bug#49542) On FreeBSD, memory mapping for MERGE tables could fail if underlying tables were empty. (Bug#47139) The my_like_range_xxx() functions returned badly formed maximum strings for Asian character sets, which caused problems for storage engines. (Bug#45012) A debugging assertion could be raised after a write failure to a closed socket. (Bug#42496) An assertion failure occurred within yaSSL for very long keys. (Bug#29784) See also Bug#53463.
2010-09-08 18:24:57 +02:00
share/mysql-test/suite/rpl/r/rpl_conditional_comments.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_create_database.result
share/mysql-test/suite/rpl/r/rpl_create_if_not_exists.result
share/mysql-test/suite/rpl/r/rpl_create_tmp_table_if_not_exists.result
share/mysql-test/suite/rpl/r/rpl_critical_errors.result
share/mysql-test/suite/rpl/r/rpl_critical_errors.result.txt
share/mysql-test/suite/rpl/r/rpl_cross_version.result
Update mysql51-{client,server} to 5.1.50. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-50.html for full changes . InnoDB Notes: InnoDB Plugin has been upgraded to version 1.0.11. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), generic Linux RPM packages, and any builds produced with the icc compiler. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: Important Change: Replication: The LOAD DATA INFILE statement is now considered unsafe for statement-based replication. When using statement-based logging mode, the statement now produces a warning; when using mixed-format logging, the statement is made using the row-based format. (Bug#34283) Partitioning: UPDATE and INSERT statements affecting partitioned tables performed poorly when using row-based replication. (Bug#52517) Partitioning: INSERT ON DUPLICATE KEY UPDATE statements performed poorly on tables having many partitions. This was because the handler function for reading a row from a specific index was not optimized in the partitioning handler. (Bug#52455) The server could crash on shutdown, if started with --innodb-use-system-malloc=0. (Bug#55581) GROUP BY operations used max_sort_length inconsistently. (Bug#55188) Building MySQL on Solaris 8 x86 failed when using Sun Studio due to gcc inline assembler code. (Bug#55061) In debug builds, an assertion could be raised when the server tried to send an OK packet to the client after having failed to detect errors during processing of the WHERE condition of an UPDATE statement. (Bug#54734) The database server could crash when renaming a table that had active transactions. (This issue only affected the database server when built for debugging.) (Bug#54453) The server could crash during the recovery phase of startup, if it previously crashed while inserting BLOB or other large columns that use off-page storage into an InnoDB table created with ROW_FORMAT=REDUNDANT or ROW_FORMAT=COMPACT. (Bug#54408) For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#54358) A client could supply data in chunks to a prepared statement parameter other than of type TEXT or BLOB using the mysql_stmt_send_long_data() C API function (or COM_STMT_SEND_LONG_DATA command). This led to a crash because other data types are not valid for long data. (Bug#54041) mysql_secure_installation did not properly identify local accounts and could incorrectly remove nonlocal root accounts. (Bug#54004) Transactions could be incorrectly committed during recovery, rather than rolled back, if the server crashed and was restarted after performing ALTER TABLE...ADD PRIMARY KEY on an InnoDB table, or some other operation that involves copying the entire table. (Bug#53756) Portability problems in SHOW STATUS could lead to incorrect results on some platforms. (Bug#53493) Builds of MySQL generated a large number of warnings. (Bug#53445) With lower_case_table_names set to a nonzero value, searches for table or database names in INFORMATION_SCHEMA tables could produce incorrect results. (Bug#53095) The ABI check for MySQL failed to compile with gcc 4.5. (Bug#52514) mysql_secure_installation sometimes failed to locate the mysql client. (Bug#52274) Reading a ucs2 data file with LOAD DATA INFILE was subject to three problems. 1) Incorrect parsing of the file as ucs2 data, resulting in incorrect length of the parsed string. This is fixed by truncating the invalid trailing bytes (incomplete multibyte characters) when reading from the file. 2) Reads from a proper ucs2 file did not recognize newline characters. This is fixed by first checking whether a byte is a newline (or any other special character) before reading it as a part of a multibyte character. 3) When using user variables to hold column data, the character set of the user variable was set incorrectly to the database charset. This is fixed by setting it to the character set specified in the LOAD DATA INFILE statement, if any. (Bug#51876) Searches in INFORMATION_SCHEMA tables for rows matching a nonexistent database produced an error instead of an empty query result. (Bug#49542) On FreeBSD, memory mapping for MERGE tables could fail if underlying tables were empty. (Bug#47139) The my_like_range_xxx() functions returned badly formed maximum strings for Asian character sets, which caused problems for storage engines. (Bug#45012) A debugging assertion could be raised after a write failure to a closed socket. (Bug#42496) An assertion failure occurred within yaSSL for very long keys. (Bug#29784) See also Bug#53463.
2010-09-08 18:24:57 +02:00
share/mysql-test/suite/rpl/r/rpl_current_user.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_ddl.result
share/mysql-test/suite/rpl/r/rpl_deadlock_innodb.result
share/mysql-test/suite/rpl/r/rpl_delete_no_where.result
share/mysql-test/suite/rpl/r/rpl_do_grant.result
share/mysql-test/suite/rpl/r/rpl_drop.result
share/mysql-test/suite/rpl/r/rpl_drop_db.result
share/mysql-test/suite/rpl/r/rpl_drop_temp.result
share/mysql-test/suite/rpl/r/rpl_drop_view.result
share/mysql-test/suite/rpl/r/rpl_dual_pos_advance.result
share/mysql-test/suite/rpl/r/rpl_empty_master_crash.result
share/mysql-test/suite/rpl/r/rpl_err_ignoredtable.result
share/mysql-test/suite/rpl/r/rpl_events.result
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/rpl/r/rpl_extra_col_master_innodb.result
share/mysql-test/suite/rpl/r/rpl_extra_col_master_myisam.result
share/mysql-test/suite/rpl/r/rpl_extra_col_slave_innodb.result
share/mysql-test/suite/rpl/r/rpl_extra_col_slave_myisam.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_failed_optimize.result
share/mysql-test/suite/rpl/r/rpl_filter_tables_not_exist.result
share/mysql-test/suite/rpl/r/rpl_flushlog_loop.result
share/mysql-test/suite/rpl/r/rpl_foreign_key_innodb.result
share/mysql-test/suite/rpl/r/rpl_found_rows.result
share/mysql-test/suite/rpl/r/rpl_free_items.result
share/mysql-test/suite/rpl/r/rpl_geometry.result
share/mysql-test/suite/rpl/r/rpl_get_lock.result
share/mysql-test/suite/rpl/r/rpl_get_master_version_and_clock.result
share/mysql-test/suite/rpl/r/rpl_grant.result
share/mysql-test/suite/rpl/r/rpl_idempotency.result
share/mysql-test/suite/rpl/r/rpl_ignore_grant.result
share/mysql-test/suite/rpl/r/rpl_ignore_revoke.result
share/mysql-test/suite/rpl/r/rpl_ignore_table.result
share/mysql-test/suite/rpl/r/rpl_ignore_table_update.result
share/mysql-test/suite/rpl/r/rpl_incident.result
share/mysql-test/suite/rpl/r/rpl_init_slave.result
share/mysql-test/suite/rpl/r/rpl_init_slave_errors.result
share/mysql-test/suite/rpl/r/rpl_innodb.result
share/mysql-test/suite/rpl/r/rpl_innodb_bug28430.result
share/mysql-test/suite/rpl/r/rpl_innodb_bug30888.result
share/mysql-test/suite/rpl/r/rpl_innodb_mixed_ddl.result
share/mysql-test/suite/rpl/r/rpl_innodb_mixed_dml.result
share/mysql-test/suite/rpl/r/rpl_insert.result
Update MySQL package to 5.1.56. Functionality added or changed: * mysqldump --xml now displays comments from column definitions. (Bug #13618) Bugs fixed: * InnoDB Storage Engine: InnoDB returned values for ¡Èrows examined¡É in the query plan that were higher than expected. NULL values were treated in an inconsistent way. The inaccurate statistics could trigger ¡Èfalse positives¡É in combination with the MAX_JOIN_SIZE setting, because the queries did not really examine as many rows as reported. (Bug #30423) * Partitioning: Trying to use the same column more than once in the partitioning key when partitioning a table by KEY caused mysqld to crash. Such duplication of key columns is now expressly disallowed, and fails with an appropriate error. (Bug #53354, Bug #57924) * Replication: When using the statement-based logging format, INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements affecting transactional tables that did not fail were not written to the binary log if they did not insert any rows. (With statement-based logging, all successful statements should be logged, whether they do or do not cause any rows to be changed.) (Bug #59338) * Replication: Formerly, STOP SLAVE stopped the slave I/O thread first and then stopped the slave SQL thread; thus, it was possible for the I/O thread to stop after replicating only part of a transaction which the SQL thread was executing, in wich case¡½if the transaction could not be rolled back safely¡½the SQL thread could hang. Now, STOP SLAVE stops the slave SQL thread first and then stops the I/O thread; this guarantees that the I/O thread can fetch any remaining events in the transaction that the SQL thread is executing, so that the SQL thread can finish the transaction if it cannot be rolled back safely. (Bug #58546) * A query of the following form returned an incorrect result, where the values for col_name in the result set were entirely replaced with NULL values: SELECT DISTINCT col_name ... ORDER BY col_name DESC; (Bug #59308, Bug #11766241) * DELETE or UPDATE statements could fail if they used DATE or DATETIME values with a year, month, or day part of zero. (Bug #59173) * The ESCAPE clause for the LIKE operator allows only expressions that evaluate to a constant at execution time, but aggregrate functions were not being rejected. (Bug #59149) * Memory leaks detected by Valgrind, some of which could cause incorrect query results, were corrected. (Bug #59110, Bug #11766075) mysqlslap failed to check for a NULL return from mysql_store_result() and crashed trying to process the result set. (Bug #59109) * In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could cause a server crash. (Bug #58371) * When mysqldadmin was run with the --sleep and --count options, it went into an infinite loop executing the specified command. (Bug #58221) * Some string manipulating SQL functions use a shared string object intended to contain an immutable empty string. This object was used by the SQL function SUBSTRING_INDEX() to return an empty string when one argument was of the wrong datatype. If the string object was then modified by the SQL function INSERT(), undefined behavior ensued. (Bug #58165, Bug #11765225) * Parsing nested regular expressions could lead to recursion resulting in a stack overflow crash. (Bug #58026, Bug #11765099) * The mysql client went into an infinite loop if the standard input was a directory. (Bug #57450) * The expression const1 BETWEEN const2 AND field was optimized incorrectly and produced incorrect results. (Bug #57030, Bug #11764215) * Some RPM installation scripts used a hardcoded value for the data directory, which could result in a failed installation for users who have a nonstandard data directory location. The same was true for other configuration values such as the PID file name. (Bug #56581, Bug #11763817) * On FreeBSD and OpenBSD, the server incorrectly checked the range of the system date, causing legal values to be rejected. (Bug #55755, Bug #11763089) * When using ExtractValue() or UpdateXML(), if the XML to be read contained an incomplete XML comment, MySQL read beyond the end of the XML string when processing, leading to a crash of the server. (Bug #44332)
2011-03-08 15:06:43 +01:00
share/mysql-test/suite/rpl/r/rpl_insert_duplicate.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_insert_id.result
share/mysql-test/suite/rpl/r/rpl_insert_id_pk.result
share/mysql-test/suite/rpl/r/rpl_insert_ignore.result
share/mysql-test/suite/rpl/r/rpl_insert_select.result
share/mysql-test/suite/rpl/r/rpl_invoked_features.result
share/mysql-test/suite/rpl/r/rpl_killed_ddl.result
share/mysql-test/suite/rpl/r/rpl_known_bugs_detection.result
share/mysql-test/suite/rpl/r/rpl_load_from_master.result
share/mysql-test/suite/rpl/r/rpl_load_table_from_master.result
share/mysql-test/suite/rpl/r/rpl_loaddata.result
share/mysql-test/suite/rpl/r/rpl_loaddata_charset.result
share/mysql-test/suite/rpl/r/rpl_loaddata_concurrent.result
share/mysql-test/suite/rpl/r/rpl_loaddata_fatal.result
share/mysql-test/suite/rpl/r/rpl_loaddata_m.result
share/mysql-test/suite/rpl/r/rpl_loaddata_map.result
share/mysql-test/suite/rpl/r/rpl_loaddata_s.result
share/mysql-test/suite/rpl/r/rpl_loaddata_simple.result
share/mysql-test/suite/rpl/r/rpl_loaddata_symlink.result
share/mysql-test/suite/rpl/r/rpl_loaddatalocal.result
share/mysql-test/suite/rpl/r/rpl_loadfile.result
share/mysql-test/suite/rpl/r/rpl_locale.result
share/mysql-test/suite/rpl/r/rpl_log_pos.result
share/mysql-test/suite/rpl/r/rpl_manual_change_index_file.result
share/mysql-test/suite/rpl/r/rpl_many_optimize.result
share/mysql-test/suite/rpl/r/rpl_master_pos_wait.result
share/mysql-test/suite/rpl/r/rpl_misc_functions.result
share/mysql-test/suite/rpl/r/rpl_mixed_bit_pk.result
share/mysql-test/suite/rpl/r/rpl_mixed_ddl_dml.result
share/mysql-test/suite/rpl/r/rpl_multi_delete.result
share/mysql-test/suite/rpl/r/rpl_multi_delete2.result
share/mysql-test/suite/rpl/r/rpl_multi_engine.result
share/mysql-test/suite/rpl/r/rpl_multi_update.result
share/mysql-test/suite/rpl/r/rpl_multi_update2.result
share/mysql-test/suite/rpl/r/rpl_multi_update3.result
share/mysql-test/suite/rpl/r/rpl_multi_update4.result
share/mysql-test/suite/rpl/r/rpl_mysql_upgrade.result
share/mysql-test/suite/rpl/r/rpl_name_const.result
share/mysql-test/suite/rpl/r/rpl_nondeterministic_functions.result
share/mysql-test/suite/rpl/r/rpl_not_null_innodb.result
share/mysql-test/suite/rpl/r/rpl_not_null_myisam.result
share/mysql-test/suite/rpl/r/rpl_optimize.result
share/mysql-test/suite/rpl/r/rpl_packet.result
Update mysql51 to 5.1.65. While here, let to use OpenSSL instead of internal yaSSL with ssl option, may related to PR 46912. Changes in MySQL 5.1.65 (2012-08-09) Functionality Added or Changed * Important Change: The YEAR(2) data type is now deprecated because it is problematic. Support for YEAR(2) will be removed in a future release of MySQL. For more information, see Section 11.3.4, "YEAR(2) Limitations and Migrating to YEAR(4)". Bugs Fixed * The server did not build with gcc 4.7. (Bug #14238406) Changes in MySQL 5.1.64 (Not released) Functionality Added or Changed * Important Change: Replication: The SHOW BINARY LOGS statement (and its equivalent SHOW MASTER LOGS) may now be executed by a user with the REPLICATION CLIENT privilege. (Formerly, the SUPER privilege was necessary to use either form of this statement.)
2012-09-15 16:48:57 +02:00
share/mysql-test/suite/rpl/r/rpl_parallel_show_binlog_events_purge_logs.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_plugin_load.result
share/mysql-test/suite/rpl/r/rpl_ps.result
share/mysql-test/suite/rpl/r/rpl_rbr_to_sbr.result
share/mysql-test/suite/rpl/r/rpl_read_only.result
share/mysql-test/suite/rpl/r/rpl_relay_space_innodb.result
share/mysql-test/suite/rpl/r/rpl_relay_space_myisam.result
share/mysql-test/suite/rpl/r/rpl_relayrotate.result
share/mysql-test/suite/rpl/r/rpl_relayspace.result
share/mysql-test/suite/rpl/r/rpl_replicate_do.result
share/mysql-test/suite/rpl/r/rpl_replicate_ignore_db.result
share/mysql-test/suite/rpl/r/rpl_report.result
share/mysql-test/suite/rpl/r/rpl_rewrt_db.result
share/mysql-test/suite/rpl/r/rpl_rotate_logs.result
share/mysql-test/suite/rpl/r/rpl_row_001.result
share/mysql-test/suite/rpl/r/rpl_row_4_bytes.result
share/mysql-test/suite/rpl/r/rpl_row_NOW.result
share/mysql-test/suite/rpl/r/rpl_row_USER.result
share/mysql-test/suite/rpl/r/rpl_row_UUID.result
share/mysql-test/suite/rpl/r/rpl_row_basic_11bugs-master.opt
share/mysql-test/suite/rpl/r/rpl_row_basic_11bugs-slave.opt
share/mysql-test/suite/rpl/r/rpl_row_basic_11bugs.result
share/mysql-test/suite/rpl/r/rpl_row_basic_2myisam.result
share/mysql-test/suite/rpl/r/rpl_row_basic_3innodb.result
share/mysql-test/suite/rpl/r/rpl_row_basic_8partition.result
share/mysql-test/suite/rpl/r/rpl_row_blob_innodb.result
share/mysql-test/suite/rpl/r/rpl_row_blob_myisam.result
share/mysql-test/suite/rpl/r/rpl_row_colSize.result
share/mysql-test/suite/rpl/r/rpl_row_conflicts.result
Changes 5.1.60: * Upgrading from an Advanced GPL RPM package to an Advanced RPM package did not work. Now on Linux it is possible to use rpm -U to replace any installed MySQL product by any other of the same release family. It is not necessary to remove the old produce with rpm -e first. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. Bugs Fixed * Important Change: InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Replication: Issuing the following statements, in the order shown, could cause a deadlock between the user thread and I/O thread. * more...
2011-12-02 15:25:09 +01:00
share/mysql-test/suite/rpl/r/rpl_row_corruption.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_row_create_table.result
share/mysql-test/suite/rpl/r/rpl_row_delayed_ins.result
share/mysql-test/suite/rpl/r/rpl_row_drop.result
share/mysql-test/suite/rpl/r/rpl_row_err_ignoredtable.result
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/rpl/r/rpl_row_find_row.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_row_flsh_tbls.result
share/mysql-test/suite/rpl/r/rpl_row_func001.result
share/mysql-test/suite/rpl/r/rpl_row_func002.result
share/mysql-test/suite/rpl/r/rpl_row_func003.result
share/mysql-test/suite/rpl/r/rpl_row_inexist_tbl.result
share/mysql-test/suite/rpl/r/rpl_row_insert_delayed.result
share/mysql-test/suite/rpl/r/rpl_row_loaddata_m.result
share/mysql-test/suite/rpl/r/rpl_row_log.result
share/mysql-test/suite/rpl/r/rpl_row_log_innodb.result
share/mysql-test/suite/rpl/r/rpl_row_max_relay_size.result
share/mysql-test/suite/rpl/r/rpl_row_multi_query.result
share/mysql-test/suite/rpl/r/rpl_row_mysqlbinlog.result
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/suite/rpl/r/rpl_row_rec_comp_innodb.result
share/mysql-test/suite/rpl/r/rpl_row_rec_comp_myisam.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_row_reset_slave.result
share/mysql-test/suite/rpl/r/rpl_row_sp001.result
share/mysql-test/suite/rpl/r/rpl_row_sp002_innodb.result
share/mysql-test/suite/rpl/r/rpl_row_sp003.result
share/mysql-test/suite/rpl/r/rpl_row_sp005.result
share/mysql-test/suite/rpl/r/rpl_row_sp006_InnoDB.result
share/mysql-test/suite/rpl/r/rpl_row_sp007_innodb.result
share/mysql-test/suite/rpl/r/rpl_row_sp008.result
share/mysql-test/suite/rpl/r/rpl_row_sp009.result
share/mysql-test/suite/rpl/r/rpl_row_sp010.result
share/mysql-test/suite/rpl/r/rpl_row_sp011.result
share/mysql-test/suite/rpl/r/rpl_row_sp012.result
share/mysql-test/suite/rpl/r/rpl_row_stop_middle_update.result
share/mysql-test/suite/rpl/r/rpl_row_tabledefs_2myisam.result
share/mysql-test/suite/rpl/r/rpl_row_tabledefs_3innodb.result
share/mysql-test/suite/rpl/r/rpl_row_tabledefs_7ndb.result
share/mysql-test/suite/rpl/r/rpl_row_tbl_metadata.result
share/mysql-test/suite/rpl/r/rpl_row_trig001.result
share/mysql-test/suite/rpl/r/rpl_row_trig002.result
share/mysql-test/suite/rpl/r/rpl_row_trig003.result
share/mysql-test/suite/rpl/r/rpl_row_trig004.result
share/mysql-test/suite/rpl/r/rpl_row_trunc_temp.result
share/mysql-test/suite/rpl/r/rpl_row_unsafe_funcs.result
share/mysql-test/suite/rpl/r/rpl_row_until.result
share/mysql-test/suite/rpl/r/rpl_row_view01.result
share/mysql-test/suite/rpl/r/rpl_row_wide_table.result
share/mysql-test/suite/rpl/r/rpl_server_id1.result
share/mysql-test/suite/rpl/r/rpl_server_id2.result
share/mysql-test/suite/rpl/r/rpl_session_var.result
share/mysql-test/suite/rpl/r/rpl_set_charset.result
share/mysql-test/suite/rpl/r/rpl_set_null_innodb.result
share/mysql-test/suite/rpl/r/rpl_set_null_myisam.result
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/suite/rpl/r/rpl_show_slave_running.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_skip_error.result
share/mysql-test/suite/rpl/r/rpl_slave_grp_exec.result
share/mysql-test/suite/rpl/r/rpl_slave_load_in.result
share/mysql-test/suite/rpl/r/rpl_slave_load_remove_tmpfile.result
share/mysql-test/suite/rpl/r/rpl_slave_load_tmpdir_not_exist.result
share/mysql-test/suite/rpl/r/rpl_slave_skip.result
share/mysql-test/suite/rpl/r/rpl_slave_status.result
Update mysql51-client/mysql51-server package to 5.1.45. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html Added a patch for recent security problem to mysql51-server, too. http://secunia.com/advisories/39454
2010-04-21 00:58:10 +02:00
share/mysql-test/suite/rpl/r/rpl_slow_query_log.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_sp.result
share/mysql-test/suite/rpl/r/rpl_sp004.result
share/mysql-test/suite/rpl/r/rpl_sp_effects.result
share/mysql-test/suite/rpl/r/rpl_sporadic_master.result
share/mysql-test/suite/rpl/r/rpl_ssl.result
share/mysql-test/suite/rpl/r/rpl_ssl1.result
share/mysql-test/suite/rpl/r/rpl_start_stop_slave.result
share/mysql-test/suite/rpl/r/rpl_stm_000001.result
share/mysql-test/suite/rpl/r/rpl_stm_EE_err2.result
share/mysql-test/suite/rpl/r/rpl_stm_auto_increment_bug33029.result
share/mysql-test/suite/rpl/r/rpl_stm_binlog_direct.result
share/mysql-test/suite/rpl/r/rpl_stm_conflicts.result
Update mysql51-{client,server} package to 5.1.51, MySQL 5.1.51. For full changes, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html Here is summary for security fixes: * Security Fix: During evaluation of arguments to extreme-value functions (such as LEAST() and GREATEST()), type errors did not propagate properly, causing the server to crash. (Bug#55826) * Security Fix: The server could crash after materializing a derived table that required a temporary table for grouping. (Bug#55568) * Security Fix: A user-variable assignment expression that is evaluated in a logical expression context can be precalculated in a temporary table for GROUP BY. However, when the expression value is used after creation of the temporary table, it was re-evaluated, not read from the table and a server crash resulted. (Bug#55564) * Security Fix: Pre-evaluation of LIKE predicates during view preparation could cause a server crash. (Bug#54568) * Security Fix: GROUP_CONCAT() and WITH ROLLUP together could cause a server crash. (Bug#54476) * Security Fix: Queries could cause a server crash if the GREATEST() or LEAST() function had a mixed list of numeric and LONGBLOB arguments, and the result of such a function was processed using an intermediate temporary table. (Bug#54461) * Security Fix: Queries with nested joins could cause an infinite loop in the server when used from stored procedures and prepared statements. (Bug#53544) * Security Fix: The PolyFromWKB() function could crash the server when improper WKB data was passed to the function. (Bug#51875)
2010-10-06 14:37:58 +02:00
share/mysql-test/suite/rpl/r/rpl_stm_create_if_not_exists.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_stm_flsh_tbls.result
share/mysql-test/suite/rpl/r/rpl_stm_insert_delayed.result
share/mysql-test/suite/rpl/r/rpl_stm_loadfile.result
share/mysql-test/suite/rpl/r/rpl_stm_log.result
share/mysql-test/suite/rpl/r/rpl_stm_max_relay_size.result
share/mysql-test/suite/rpl/r/rpl_stm_mixing_engines.result
share/mysql-test/suite/rpl/r/rpl_stm_multi_query.result
share/mysql-test/suite/rpl/r/rpl_stm_no_op.result
Update mysql51-{client,server} to 5.1.63 (MySQL 5.1.63). Changes (http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html): * Security Fix: Bug #64884 was fixed. * Security Fix: Bug #59387 was fixed. * InnoDB: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. (Bug #13847885) * InnoDB: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. (Bug #12861864, Bug #11766019) * InnoDB: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. (Bug #11766634, Bug #59783) * Partitioning: After updating a row of a partitioned table and selecting that row within the same transaction with the query cache enabled, then performing a ROLLBACK, the same result was returned by an identical SELECT issued in a new transaction. (Bug #11761296, Bug #53775) * Replication: The --relay-log-space-limit option was sometimes ignored. More specifically, when the SQL thread went to sleep, it allowed the I/O thread to queue additional events in such a way that the relay log space limit was bypassed, and the number of events in the queue could grow well past the point where the relay logs needed to be rotated. Now in such cases, the SQL thread checks to see whether the I/O thread should rotate and provide the SQL thread a chance to purge the logs (thus freeing space). Note that, when the SQL thread is in the middle of a transaction, it cannot purge the logs; it can only ask for more events until the transaction is complete. Once the transaction is finished, the SQL thread can immediately instruct the I/O thread to rotate. (Bug #12400313, Bug #64503) References: See also Bug #13806492. * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored procedures on slave servers could cause replication failures. (Bug #12601974) * If the system time was adjusted backward during query execution, the apparent execution time could be negative. But in some cases these queries would be written to the slow query log, with the negative execution time written as a large unsigned number. Now statements with apparent negative execution time are not written to the slow query log. (Bug #63524, Bug #13454045) References: See also Bug #27208. * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * SHOW statements treated stored procedure, stored function, and event names as case sensitive. (Bug #56224, Bug #11763507) * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 14:59:39 +02:00
share/mysql-test/suite/rpl/r/rpl_stm_relay_ign_space.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_stm_reset_slave.result
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/suite/rpl/r/rpl_stm_sql_mode.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_stm_until.result
Update mysql51-{client,server} to 5.1.53. Most changes are related to replication and seems to no security fix. For more detail, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html
2010-11-26 14:52:58 +01:00
share/mysql-test/suite/rpl/r/rpl_stop_slave.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_switch_stm_row_mixed.result
share/mysql-test/suite/rpl/r/rpl_temp_table.result
share/mysql-test/suite/rpl/r/rpl_temp_table_mix_row.result
share/mysql-test/suite/rpl/r/rpl_temporary.result
share/mysql-test/suite/rpl/r/rpl_temporary_errors.result
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/rpl/r/rpl_test_framework.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_timezone.result
share/mysql-test/suite/rpl/r/rpl_tmp_table_and_DDL.result
share/mysql-test/suite/rpl/r/rpl_trigger.result
share/mysql-test/suite/rpl/r/rpl_trunc_temp.result
share/mysql-test/suite/rpl/r/rpl_truncate_2myisam.result
share/mysql-test/suite/rpl/r/rpl_truncate_3innodb.result
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/suite/rpl/r/rpl_typeconv_innodb.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/r/rpl_udf.result
share/mysql-test/suite/rpl/r/rpl_user.result
share/mysql-test/suite/rpl/r/rpl_user_variables.result
share/mysql-test/suite/rpl/r/rpl_variables.result
share/mysql-test/suite/rpl/r/rpl_variables_stm.result
share/mysql-test/suite/rpl/r/rpl_view.result
share/mysql-test/suite/rpl/rpl_1slave_base.cnf
share/mysql-test/suite/rpl/t/disabled.def
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/rpl/t/rpl_000010-slave.opt
share/mysql-test/suite/rpl/t/rpl_000010.test
share/mysql-test/suite/rpl/t/rpl_000011.test
share/mysql-test/suite/rpl/t/rpl_000013.test
share/mysql-test/suite/rpl/t/rpl_000017-slave.opt
share/mysql-test/suite/rpl/t/rpl_000017.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_EE_err.test
share/mysql-test/suite/rpl/t/rpl_LD_INFILE.test
share/mysql-test/suite/rpl/t/rpl_alter.test
share/mysql-test/suite/rpl/t/rpl_alter_db.test
share/mysql-test/suite/rpl/t/rpl_auto_increment-master.opt
share/mysql-test/suite/rpl/t/rpl_auto_increment.test
share/mysql-test/suite/rpl/t/rpl_auto_increment_11932.test
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/rpl/t/rpl_auto_increment_bug33029.test
Update mysql51 to 5.1.65. While here, let to use OpenSSL instead of internal yaSSL with ssl option, may related to PR 46912. Changes in MySQL 5.1.65 (2012-08-09) Functionality Added or Changed * Important Change: The YEAR(2) data type is now deprecated because it is problematic. Support for YEAR(2) will be removed in a future release of MySQL. For more information, see Section 11.3.4, "YEAR(2) Limitations and Migrating to YEAR(4)". Bugs Fixed * The server did not build with gcc 4.7. (Bug #14238406) Changes in MySQL 5.1.64 (Not released) Functionality Added or Changed * Important Change: Replication: The SHOW BINARY LOGS statement (and its equivalent SHOW MASTER LOGS) may now be executed by a user with the REPLICATION CLIENT privilege. (Formerly, the SUPER privilege was necessary to use either form of this statement.)
2012-09-15 16:48:57 +02:00
share/mysql-test/suite/rpl/t/rpl_auto_increment_bug45679.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_auto_increment_update_failure.test
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/suite/rpl/t/rpl_begin_commit_rollback-master.opt
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_begin_commit_rollback-slave.opt
share/mysql-test/suite/rpl/t/rpl_begin_commit_rollback.test
share/mysql-test/suite/rpl/t/rpl_binlog_corruption.test
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/rpl/t/rpl_binlog_errors-master.opt
share/mysql-test/suite/rpl/t/rpl_binlog_errors.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_binlog_grant.test
share/mysql-test/suite/rpl/t/rpl_binlog_max_cache_size.test
share/mysql-test/suite/rpl/t/rpl_bit.test
share/mysql-test/suite/rpl/t/rpl_bit_npk.test
share/mysql-test/suite/rpl/t/rpl_blackhole.test
share/mysql-test/suite/rpl/t/rpl_bug26395.test
share/mysql-test/suite/rpl/t/rpl_bug31076.test
share/mysql-test/suite/rpl/t/rpl_bug33931.test
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/suite/rpl/t/rpl_bug37426.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_bug38694-slave.opt
share/mysql-test/suite/rpl/t/rpl_bug38694.test
share/mysql-test/suite/rpl/t/rpl_change_master.test
share/mysql-test/suite/rpl/t/rpl_charset.test
share/mysql-test/suite/rpl/t/rpl_charset_sjis.test
share/mysql-test/suite/rpl/t/rpl_circular_for_4_hosts.cnf
share/mysql-test/suite/rpl/t/rpl_circular_for_4_hosts.test
share/mysql-test/suite/rpl/t/rpl_colSize.test
share/mysql-test/suite/rpl/t/rpl_commit_after_flush.test
share/mysql-test/suite/rpl/t/rpl_concurrency_error-master.opt
share/mysql-test/suite/rpl/t/rpl_concurrency_error.test
Update mysql51-{client,server} to 5.1.50. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-50.html for full changes . InnoDB Notes: InnoDB Plugin has been upgraded to version 1.0.11. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), generic Linux RPM packages, and any builds produced with the icc compiler. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: Important Change: Replication: The LOAD DATA INFILE statement is now considered unsafe for statement-based replication. When using statement-based logging mode, the statement now produces a warning; when using mixed-format logging, the statement is made using the row-based format. (Bug#34283) Partitioning: UPDATE and INSERT statements affecting partitioned tables performed poorly when using row-based replication. (Bug#52517) Partitioning: INSERT ON DUPLICATE KEY UPDATE statements performed poorly on tables having many partitions. This was because the handler function for reading a row from a specific index was not optimized in the partitioning handler. (Bug#52455) The server could crash on shutdown, if started with --innodb-use-system-malloc=0. (Bug#55581) GROUP BY operations used max_sort_length inconsistently. (Bug#55188) Building MySQL on Solaris 8 x86 failed when using Sun Studio due to gcc inline assembler code. (Bug#55061) In debug builds, an assertion could be raised when the server tried to send an OK packet to the client after having failed to detect errors during processing of the WHERE condition of an UPDATE statement. (Bug#54734) The database server could crash when renaming a table that had active transactions. (This issue only affected the database server when built for debugging.) (Bug#54453) The server could crash during the recovery phase of startup, if it previously crashed while inserting BLOB or other large columns that use off-page storage into an InnoDB table created with ROW_FORMAT=REDUNDANT or ROW_FORMAT=COMPACT. (Bug#54408) For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#54358) A client could supply data in chunks to a prepared statement parameter other than of type TEXT or BLOB using the mysql_stmt_send_long_data() C API function (or COM_STMT_SEND_LONG_DATA command). This led to a crash because other data types are not valid for long data. (Bug#54041) mysql_secure_installation did not properly identify local accounts and could incorrectly remove nonlocal root accounts. (Bug#54004) Transactions could be incorrectly committed during recovery, rather than rolled back, if the server crashed and was restarted after performing ALTER TABLE...ADD PRIMARY KEY on an InnoDB table, or some other operation that involves copying the entire table. (Bug#53756) Portability problems in SHOW STATUS could lead to incorrect results on some platforms. (Bug#53493) Builds of MySQL generated a large number of warnings. (Bug#53445) With lower_case_table_names set to a nonzero value, searches for table or database names in INFORMATION_SCHEMA tables could produce incorrect results. (Bug#53095) The ABI check for MySQL failed to compile with gcc 4.5. (Bug#52514) mysql_secure_installation sometimes failed to locate the mysql client. (Bug#52274) Reading a ucs2 data file with LOAD DATA INFILE was subject to three problems. 1) Incorrect parsing of the file as ucs2 data, resulting in incorrect length of the parsed string. This is fixed by truncating the invalid trailing bytes (incomplete multibyte characters) when reading from the file. 2) Reads from a proper ucs2 file did not recognize newline characters. This is fixed by first checking whether a byte is a newline (or any other special character) before reading it as a part of a multibyte character. 3) When using user variables to hold column data, the character set of the user variable was set incorrectly to the database charset. This is fixed by setting it to the character set specified in the LOAD DATA INFILE statement, if any. (Bug#51876) Searches in INFORMATION_SCHEMA tables for rows matching a nonexistent database produced an error instead of an empty query result. (Bug#49542) On FreeBSD, memory mapping for MERGE tables could fail if underlying tables were empty. (Bug#47139) The my_like_range_xxx() functions returned badly formed maximum strings for Asian character sets, which caused problems for storage engines. (Bug#45012) A debugging assertion could be raised after a write failure to a closed socket. (Bug#42496) An assertion failure occurred within yaSSL for very long keys. (Bug#29784) See also Bug#53463.
2010-09-08 18:24:57 +02:00
share/mysql-test/suite/rpl/t/rpl_conditional_comments.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_create_database-master.opt
share/mysql-test/suite/rpl/t/rpl_create_database-slave.opt
share/mysql-test/suite/rpl/t/rpl_create_database.test
share/mysql-test/suite/rpl/t/rpl_create_if_not_exists.test
share/mysql-test/suite/rpl/t/rpl_create_tmp_table_if_not_exists.test
share/mysql-test/suite/rpl/t/rpl_critical_errors.test
share/mysql-test/suite/rpl/t/rpl_cross_version-master.opt
share/mysql-test/suite/rpl/t/rpl_cross_version.test
Update mysql51-{client,server} package to 5.1.54. Functionality added or changed: * Support for the IBMDB2I storage engine has been removed. (Bug#58079) * The pstack library was nonfunctional and has been removed, along with the --with-pstack option for configure. The --enable-pstack option for mysqld is deprecated and will be removed in MySQL 5.5. (Bug#57210) Bugs fixed: * Performance: InnoDB Storage Engine: Improved concurrency when several ANALYZE TABLE or SHOW TABLE STATUS statements are run simultaneously for InnoDB tables. (Bug#53046) * InnoDB Storage Engine: For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#57799) * Partitioning: An INSERT ... ON DUPLICATE KEY UPDATE column = 0 statement on an AUTO_INCREMENT column caused the debug server to crash. (Bug#57890) * Several compilation problems were fixed. (Bug#57992, Bug#57993, Bug#57994, Bug#57995, Bug#57996, Bug#57997, Bug#58057) * Passing a string that was not null-terminated to UpdateXML() or ExtractValue() caused the server to fail with an assertion. (Bug#57279) * Queries executed using the Index Merge access method and a temporary file could return incorrect results. (Bug#56862) * The find_files() function used by SHOW statements performed redundant and unnecessary memory allocation. (Bug#51208)
2010-12-16 04:42:49 +01:00
share/mysql-test/suite/rpl/t/rpl_current_user-master.opt
Update mysql51-{client,server} to 5.1.50. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-50.html for full changes . InnoDB Notes: InnoDB Plugin has been upgraded to version 1.0.11. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), generic Linux RPM packages, and any builds produced with the icc compiler. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: Important Change: Replication: The LOAD DATA INFILE statement is now considered unsafe for statement-based replication. When using statement-based logging mode, the statement now produces a warning; when using mixed-format logging, the statement is made using the row-based format. (Bug#34283) Partitioning: UPDATE and INSERT statements affecting partitioned tables performed poorly when using row-based replication. (Bug#52517) Partitioning: INSERT ON DUPLICATE KEY UPDATE statements performed poorly on tables having many partitions. This was because the handler function for reading a row from a specific index was not optimized in the partitioning handler. (Bug#52455) The server could crash on shutdown, if started with --innodb-use-system-malloc=0. (Bug#55581) GROUP BY operations used max_sort_length inconsistently. (Bug#55188) Building MySQL on Solaris 8 x86 failed when using Sun Studio due to gcc inline assembler code. (Bug#55061) In debug builds, an assertion could be raised when the server tried to send an OK packet to the client after having failed to detect errors during processing of the WHERE condition of an UPDATE statement. (Bug#54734) The database server could crash when renaming a table that had active transactions. (This issue only affected the database server when built for debugging.) (Bug#54453) The server could crash during the recovery phase of startup, if it previously crashed while inserting BLOB or other large columns that use off-page storage into an InnoDB table created with ROW_FORMAT=REDUNDANT or ROW_FORMAT=COMPACT. (Bug#54408) For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#54358) A client could supply data in chunks to a prepared statement parameter other than of type TEXT or BLOB using the mysql_stmt_send_long_data() C API function (or COM_STMT_SEND_LONG_DATA command). This led to a crash because other data types are not valid for long data. (Bug#54041) mysql_secure_installation did not properly identify local accounts and could incorrectly remove nonlocal root accounts. (Bug#54004) Transactions could be incorrectly committed during recovery, rather than rolled back, if the server crashed and was restarted after performing ALTER TABLE...ADD PRIMARY KEY on an InnoDB table, or some other operation that involves copying the entire table. (Bug#53756) Portability problems in SHOW STATUS could lead to incorrect results on some platforms. (Bug#53493) Builds of MySQL generated a large number of warnings. (Bug#53445) With lower_case_table_names set to a nonzero value, searches for table or database names in INFORMATION_SCHEMA tables could produce incorrect results. (Bug#53095) The ABI check for MySQL failed to compile with gcc 4.5. (Bug#52514) mysql_secure_installation sometimes failed to locate the mysql client. (Bug#52274) Reading a ucs2 data file with LOAD DATA INFILE was subject to three problems. 1) Incorrect parsing of the file as ucs2 data, resulting in incorrect length of the parsed string. This is fixed by truncating the invalid trailing bytes (incomplete multibyte characters) when reading from the file. 2) Reads from a proper ucs2 file did not recognize newline characters. This is fixed by first checking whether a byte is a newline (or any other special character) before reading it as a part of a multibyte character. 3) When using user variables to hold column data, the character set of the user variable was set incorrectly to the database charset. This is fixed by setting it to the character set specified in the LOAD DATA INFILE statement, if any. (Bug#51876) Searches in INFORMATION_SCHEMA tables for rows matching a nonexistent database produced an error instead of an empty query result. (Bug#49542) On FreeBSD, memory mapping for MERGE tables could fail if underlying tables were empty. (Bug#47139) The my_like_range_xxx() functions returned badly formed maximum strings for Asian character sets, which caused problems for storage engines. (Bug#45012) A debugging assertion could be raised after a write failure to a closed socket. (Bug#42496) An assertion failure occurred within yaSSL for very long keys. (Bug#29784) See also Bug#53463.
2010-09-08 18:24:57 +02:00
share/mysql-test/suite/rpl/t/rpl_current_user.cnf
share/mysql-test/suite/rpl/t/rpl_current_user.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_ddl.test
share/mysql-test/suite/rpl/t/rpl_deadlock_innodb-slave.opt
share/mysql-test/suite/rpl/t/rpl_deadlock_innodb.test
share/mysql-test/suite/rpl/t/rpl_delete_no_where.test
share/mysql-test/suite/rpl/t/rpl_do_grant.test
share/mysql-test/suite/rpl/t/rpl_drop.test
share/mysql-test/suite/rpl/t/rpl_drop_db.test
share/mysql-test/suite/rpl/t/rpl_drop_temp-slave.opt
share/mysql-test/suite/rpl/t/rpl_drop_temp.test
share/mysql-test/suite/rpl/t/rpl_drop_view.test
share/mysql-test/suite/rpl/t/rpl_dual_pos_advance-master.opt
share/mysql-test/suite/rpl/t/rpl_dual_pos_advance.test
share/mysql-test/suite/rpl/t/rpl_empty_master_crash-master.opt
share/mysql-test/suite/rpl/t/rpl_empty_master_crash.test
share/mysql-test/suite/rpl/t/rpl_err_ignoredtable-slave.opt
share/mysql-test/suite/rpl/t/rpl_err_ignoredtable.test
share/mysql-test/suite/rpl/t/rpl_events.test
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/rpl/t/rpl_extra_col_master_innodb.test
share/mysql-test/suite/rpl/t/rpl_extra_col_master_myisam.test
share/mysql-test/suite/rpl/t/rpl_extra_col_slave_innodb.test
share/mysql-test/suite/rpl/t/rpl_extra_col_slave_myisam.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_failed_optimize-master.opt
share/mysql-test/suite/rpl/t/rpl_failed_optimize.test
share/mysql-test/suite/rpl/t/rpl_filter_tables_not_exist-slave.opt
share/mysql-test/suite/rpl/t/rpl_filter_tables_not_exist.test
share/mysql-test/suite/rpl/t/rpl_flushlog_loop-master.opt
share/mysql-test/suite/rpl/t/rpl_flushlog_loop-slave.opt
share/mysql-test/suite/rpl/t/rpl_flushlog_loop.test
share/mysql-test/suite/rpl/t/rpl_foreign_key_innodb.test
share/mysql-test/suite/rpl/t/rpl_found_rows.test
share/mysql-test/suite/rpl/t/rpl_free_items-slave.opt
share/mysql-test/suite/rpl/t/rpl_free_items.test
share/mysql-test/suite/rpl/t/rpl_geometry.test
share/mysql-test/suite/rpl/t/rpl_get_lock.test
share/mysql-test/suite/rpl/t/rpl_get_master_version_and_clock-slave.opt
share/mysql-test/suite/rpl/t/rpl_get_master_version_and_clock.test
share/mysql-test/suite/rpl/t/rpl_grant.test
share/mysql-test/suite/rpl/t/rpl_idempotency-slave.opt
share/mysql-test/suite/rpl/t/rpl_idempotency.test
share/mysql-test/suite/rpl/t/rpl_ignore_grant-slave.opt
share/mysql-test/suite/rpl/t/rpl_ignore_grant.test
share/mysql-test/suite/rpl/t/rpl_ignore_revoke-slave.opt
share/mysql-test/suite/rpl/t/rpl_ignore_revoke.test
share/mysql-test/suite/rpl/t/rpl_ignore_table-slave.opt
share/mysql-test/suite/rpl/t/rpl_ignore_table.test
share/mysql-test/suite/rpl/t/rpl_ignore_table_update-slave.opt
share/mysql-test/suite/rpl/t/rpl_ignore_table_update.test
share/mysql-test/suite/rpl/t/rpl_incident-master.opt
share/mysql-test/suite/rpl/t/rpl_incident.test
share/mysql-test/suite/rpl/t/rpl_init_slave-slave.opt
share/mysql-test/suite/rpl/t/rpl_init_slave.test
share/mysql-test/suite/rpl/t/rpl_init_slave_errors.test
share/mysql-test/suite/rpl/t/rpl_innodb-master.opt
share/mysql-test/suite/rpl/t/rpl_innodb.test
share/mysql-test/suite/rpl/t/rpl_innodb_bug28430-master.opt
share/mysql-test/suite/rpl/t/rpl_innodb_bug28430-slave.opt
share/mysql-test/suite/rpl/t/rpl_innodb_bug28430.test
share/mysql-test/suite/rpl/t/rpl_innodb_bug30888.test
share/mysql-test/suite/rpl/t/rpl_innodb_mixed_ddl.test
share/mysql-test/suite/rpl/t/rpl_innodb_mixed_dml.test
share/mysql-test/suite/rpl/t/rpl_insert.test
Update MySQL package to 5.1.56. Functionality added or changed: * mysqldump --xml now displays comments from column definitions. (Bug #13618) Bugs fixed: * InnoDB Storage Engine: InnoDB returned values for ¡Èrows examined¡É in the query plan that were higher than expected. NULL values were treated in an inconsistent way. The inaccurate statistics could trigger ¡Èfalse positives¡É in combination with the MAX_JOIN_SIZE setting, because the queries did not really examine as many rows as reported. (Bug #30423) * Partitioning: Trying to use the same column more than once in the partitioning key when partitioning a table by KEY caused mysqld to crash. Such duplication of key columns is now expressly disallowed, and fails with an appropriate error. (Bug #53354, Bug #57924) * Replication: When using the statement-based logging format, INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements affecting transactional tables that did not fail were not written to the binary log if they did not insert any rows. (With statement-based logging, all successful statements should be logged, whether they do or do not cause any rows to be changed.) (Bug #59338) * Replication: Formerly, STOP SLAVE stopped the slave I/O thread first and then stopped the slave SQL thread; thus, it was possible for the I/O thread to stop after replicating only part of a transaction which the SQL thread was executing, in wich case¡½if the transaction could not be rolled back safely¡½the SQL thread could hang. Now, STOP SLAVE stops the slave SQL thread first and then stops the I/O thread; this guarantees that the I/O thread can fetch any remaining events in the transaction that the SQL thread is executing, so that the SQL thread can finish the transaction if it cannot be rolled back safely. (Bug #58546) * A query of the following form returned an incorrect result, where the values for col_name in the result set were entirely replaced with NULL values: SELECT DISTINCT col_name ... ORDER BY col_name DESC; (Bug #59308, Bug #11766241) * DELETE or UPDATE statements could fail if they used DATE or DATETIME values with a year, month, or day part of zero. (Bug #59173) * The ESCAPE clause for the LIKE operator allows only expressions that evaluate to a constant at execution time, but aggregrate functions were not being rejected. (Bug #59149) * Memory leaks detected by Valgrind, some of which could cause incorrect query results, were corrected. (Bug #59110, Bug #11766075) mysqlslap failed to check for a NULL return from mysql_store_result() and crashed trying to process the result set. (Bug #59109) * In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could cause a server crash. (Bug #58371) * When mysqldadmin was run with the --sleep and --count options, it went into an infinite loop executing the specified command. (Bug #58221) * Some string manipulating SQL functions use a shared string object intended to contain an immutable empty string. This object was used by the SQL function SUBSTRING_INDEX() to return an empty string when one argument was of the wrong datatype. If the string object was then modified by the SQL function INSERT(), undefined behavior ensued. (Bug #58165, Bug #11765225) * Parsing nested regular expressions could lead to recursion resulting in a stack overflow crash. (Bug #58026, Bug #11765099) * The mysql client went into an infinite loop if the standard input was a directory. (Bug #57450) * The expression const1 BETWEEN const2 AND field was optimized incorrectly and produced incorrect results. (Bug #57030, Bug #11764215) * Some RPM installation scripts used a hardcoded value for the data directory, which could result in a failed installation for users who have a nonstandard data directory location. The same was true for other configuration values such as the PID file name. (Bug #56581, Bug #11763817) * On FreeBSD and OpenBSD, the server incorrectly checked the range of the system date, causing legal values to be rejected. (Bug #55755, Bug #11763089) * When using ExtractValue() or UpdateXML(), if the XML to be read contained an incomplete XML comment, MySQL read beyond the end of the XML string when processing, leading to a crash of the server. (Bug #44332)
2011-03-08 15:06:43 +01:00
share/mysql-test/suite/rpl/t/rpl_insert_duplicate.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_insert_id.test
share/mysql-test/suite/rpl/t/rpl_insert_id_pk.test
share/mysql-test/suite/rpl/t/rpl_insert_ignore.test
share/mysql-test/suite/rpl/t/rpl_insert_select.test
share/mysql-test/suite/rpl/t/rpl_invoked_features.test
share/mysql-test/suite/rpl/t/rpl_killed_ddl-master.opt
share/mysql-test/suite/rpl/t/rpl_killed_ddl.test
share/mysql-test/suite/rpl/t/rpl_known_bugs_detection-master.opt
share/mysql-test/suite/rpl/t/rpl_known_bugs_detection.test
share/mysql-test/suite/rpl/t/rpl_load_from_master-slave.opt
share/mysql-test/suite/rpl/t/rpl_load_from_master.test
share/mysql-test/suite/rpl/t/rpl_load_table_from_master.test
share/mysql-test/suite/rpl/t/rpl_loaddata.test
share/mysql-test/suite/rpl/t/rpl_loaddata_charset.test
share/mysql-test/suite/rpl/t/rpl_loaddata_concurrent.test
share/mysql-test/suite/rpl/t/rpl_loaddata_fatal-slave.opt
share/mysql-test/suite/rpl/t/rpl_loaddata_fatal.test
share/mysql-test/suite/rpl/t/rpl_loaddata_m-master.opt
share/mysql-test/suite/rpl/t/rpl_loaddata_m.test
share/mysql-test/suite/rpl/t/rpl_loaddata_map-master.opt
share/mysql-test/suite/rpl/t/rpl_loaddata_map-slave.opt
share/mysql-test/suite/rpl/t/rpl_loaddata_map.test
share/mysql-test/suite/rpl/t/rpl_loaddata_s-slave.opt
share/mysql-test/suite/rpl/t/rpl_loaddata_s.test
share/mysql-test/suite/rpl/t/rpl_loaddata_simple.test
share/mysql-test/suite/rpl/t/rpl_loaddata_symlink-master.opt
share/mysql-test/suite/rpl/t/rpl_loaddata_symlink-master.sh
share/mysql-test/suite/rpl/t/rpl_loaddata_symlink-slave.opt
share/mysql-test/suite/rpl/t/rpl_loaddata_symlink-slave.sh
share/mysql-test/suite/rpl/t/rpl_loaddata_symlink.test
share/mysql-test/suite/rpl/t/rpl_loaddatalocal.test
share/mysql-test/suite/rpl/t/rpl_loadfile.test
share/mysql-test/suite/rpl/t/rpl_locale.test
share/mysql-test/suite/rpl/t/rpl_log_pos.test
share/mysql-test/suite/rpl/t/rpl_manual_change_index_file.test
share/mysql-test/suite/rpl/t/rpl_many_optimize.test
share/mysql-test/suite/rpl/t/rpl_master_pos_wait.test
share/mysql-test/suite/rpl/t/rpl_misc_functions-slave.sh
share/mysql-test/suite/rpl/t/rpl_misc_functions.test
share/mysql-test/suite/rpl/t/rpl_mixed_bit_pk.test
share/mysql-test/suite/rpl/t/rpl_mixed_ddl_dml.test
share/mysql-test/suite/rpl/t/rpl_multi_delete-slave.opt
share/mysql-test/suite/rpl/t/rpl_multi_delete.test
share/mysql-test/suite/rpl/t/rpl_multi_delete2-slave.opt
share/mysql-test/suite/rpl/t/rpl_multi_delete2.test
share/mysql-test/suite/rpl/t/rpl_multi_engine.test
share/mysql-test/suite/rpl/t/rpl_multi_update.test
share/mysql-test/suite/rpl/t/rpl_multi_update2-slave.opt
share/mysql-test/suite/rpl/t/rpl_multi_update2.test
share/mysql-test/suite/rpl/t/rpl_multi_update3.test
share/mysql-test/suite/rpl/t/rpl_multi_update4-slave.opt
share/mysql-test/suite/rpl/t/rpl_multi_update4.test
share/mysql-test/suite/rpl/t/rpl_mysql_upgrade.test
share/mysql-test/suite/rpl/t/rpl_name_const.test
share/mysql-test/suite/rpl/t/rpl_nondeterministic_functions.test
share/mysql-test/suite/rpl/t/rpl_not_null_innodb.test
share/mysql-test/suite/rpl/t/rpl_not_null_myisam.test
share/mysql-test/suite/rpl/t/rpl_optimize.test
share/mysql-test/suite/rpl/t/rpl_packet-master.opt
share/mysql-test/suite/rpl/t/rpl_packet-slave.opt
share/mysql-test/suite/rpl/t/rpl_packet.test
Update mysql51 to 5.1.65. While here, let to use OpenSSL instead of internal yaSSL with ssl option, may related to PR 46912. Changes in MySQL 5.1.65 (2012-08-09) Functionality Added or Changed * Important Change: The YEAR(2) data type is now deprecated because it is problematic. Support for YEAR(2) will be removed in a future release of MySQL. For more information, see Section 11.3.4, "YEAR(2) Limitations and Migrating to YEAR(4)". Bugs Fixed * The server did not build with gcc 4.7. (Bug #14238406) Changes in MySQL 5.1.64 (Not released) Functionality Added or Changed * Important Change: Replication: The SHOW BINARY LOGS statement (and its equivalent SHOW MASTER LOGS) may now be executed by a user with the REPLICATION CLIENT privilege. (Formerly, the SUPER privilege was necessary to use either form of this statement.)
2012-09-15 16:48:57 +02:00
share/mysql-test/suite/rpl/t/rpl_parallel_show_binlog_events_purge_logs.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_plugin_load-master.opt
share/mysql-test/suite/rpl/t/rpl_plugin_load-slave.opt
share/mysql-test/suite/rpl/t/rpl_plugin_load.test
share/mysql-test/suite/rpl/t/rpl_ps.test
share/mysql-test/suite/rpl/t/rpl_rbr_to_sbr.test
share/mysql-test/suite/rpl/t/rpl_read_only.test
share/mysql-test/suite/rpl/t/rpl_relay_space_innodb.test
share/mysql-test/suite/rpl/t/rpl_relay_space_myisam.test
share/mysql-test/suite/rpl/t/rpl_relayrotate-slave.opt
share/mysql-test/suite/rpl/t/rpl_relayrotate.test
share/mysql-test/suite/rpl/t/rpl_relayspace-slave.opt
share/mysql-test/suite/rpl/t/rpl_relayspace.test
share/mysql-test/suite/rpl/t/rpl_replicate_do-slave.opt
share/mysql-test/suite/rpl/t/rpl_replicate_do.test
share/mysql-test/suite/rpl/t/rpl_replicate_ignore_db-slave.opt
share/mysql-test/suite/rpl/t/rpl_replicate_ignore_db.test
share/mysql-test/suite/rpl/t/rpl_report-slave.opt
share/mysql-test/suite/rpl/t/rpl_report.test
share/mysql-test/suite/rpl/t/rpl_rewrt_db-slave.opt
share/mysql-test/suite/rpl/t/rpl_rewrt_db.test
share/mysql-test/suite/rpl/t/rpl_rotate_logs.cnf
share/mysql-test/suite/rpl/t/rpl_rotate_logs.test
share/mysql-test/suite/rpl/t/rpl_row_001.test
share/mysql-test/suite/rpl/t/rpl_row_4_bytes-master.opt
share/mysql-test/suite/rpl/t/rpl_row_4_bytes.test
share/mysql-test/suite/rpl/t/rpl_row_NOW.test
share/mysql-test/suite/rpl/t/rpl_row_USER.test
share/mysql-test/suite/rpl/t/rpl_row_UUID.test
share/mysql-test/suite/rpl/t/rpl_row_basic_11bugs-master.opt
share/mysql-test/suite/rpl/t/rpl_row_basic_11bugs.test
share/mysql-test/suite/rpl/t/rpl_row_basic_2myisam.test
share/mysql-test/suite/rpl/t/rpl_row_basic_3innodb.test
share/mysql-test/suite/rpl/t/rpl_row_basic_8partition.test
share/mysql-test/suite/rpl/t/rpl_row_blob_innodb.test
share/mysql-test/suite/rpl/t/rpl_row_blob_myisam.test
share/mysql-test/suite/rpl/t/rpl_row_colSize.test
share/mysql-test/suite/rpl/t/rpl_row_conflicts.test
Changes 5.1.60: * Upgrading from an Advanced GPL RPM package to an Advanced RPM package did not work. Now on Linux it is possible to use rpm -U to replace any installed MySQL product by any other of the same release family. It is not necessary to remove the old produce with rpm -e first. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. Bugs Fixed * Important Change: InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Replication: Issuing the following statements, in the order shown, could cause a deadlock between the user thread and I/O thread. * more...
2011-12-02 15:25:09 +01:00
share/mysql-test/suite/rpl/t/rpl_row_corruption-slave.opt
share/mysql-test/suite/rpl/t/rpl_row_corruption.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_row_create_table.test
share/mysql-test/suite/rpl/t/rpl_row_delayed_ins.test
share/mysql-test/suite/rpl/t/rpl_row_drop.test
share/mysql-test/suite/rpl/t/rpl_row_err_daisychain-master.opt
share/mysql-test/suite/rpl/t/rpl_row_err_daisychain-slave.opt
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/suite/rpl/t/rpl_row_find_row.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_row_flsh_tbls.test
share/mysql-test/suite/rpl/t/rpl_row_func001.test
share/mysql-test/suite/rpl/t/rpl_row_func002.test
share/mysql-test/suite/rpl/t/rpl_row_func003.test
share/mysql-test/suite/rpl/t/rpl_row_inexist_tbl.test
share/mysql-test/suite/rpl/t/rpl_row_insert_delayed.test
share/mysql-test/suite/rpl/t/rpl_row_log-master.opt
share/mysql-test/suite/rpl/t/rpl_row_log-slave.opt
share/mysql-test/suite/rpl/t/rpl_row_log.test
share/mysql-test/suite/rpl/t/rpl_row_log_innodb-master.opt
share/mysql-test/suite/rpl/t/rpl_row_log_innodb.test
share/mysql-test/suite/rpl/t/rpl_row_max_relay_size.test
share/mysql-test/suite/rpl/t/rpl_row_mysqlbinlog-master.opt
share/mysql-test/suite/rpl/t/rpl_row_mysqlbinlog.test
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/suite/rpl/t/rpl_row_rec_comp_innodb.test
share/mysql-test/suite/rpl/t/rpl_row_rec_comp_myisam.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_row_reset_slave.test
share/mysql-test/suite/rpl/t/rpl_row_sp001.test
share/mysql-test/suite/rpl/t/rpl_row_sp002_innodb.test
share/mysql-test/suite/rpl/t/rpl_row_sp003.test
share/mysql-test/suite/rpl/t/rpl_row_sp005.test
share/mysql-test/suite/rpl/t/rpl_row_sp006_InnoDB.test
share/mysql-test/suite/rpl/t/rpl_row_sp007_innodb.test
share/mysql-test/suite/rpl/t/rpl_row_sp008.test
share/mysql-test/suite/rpl/t/rpl_row_sp009.test
share/mysql-test/suite/rpl/t/rpl_row_sp010.test
share/mysql-test/suite/rpl/t/rpl_row_sp011.test
share/mysql-test/suite/rpl/t/rpl_row_sp012.test
share/mysql-test/suite/rpl/t/rpl_row_stop_middle_update-master.opt
share/mysql-test/suite/rpl/t/rpl_row_stop_middle_update-slave.opt
share/mysql-test/suite/rpl/t/rpl_row_stop_middle_update.test
share/mysql-test/suite/rpl/t/rpl_row_tabledefs_2myisam.test
share/mysql-test/suite/rpl/t/rpl_row_tabledefs_3innodb.test
share/mysql-test/suite/rpl/t/rpl_row_tbl_metadata.test
share/mysql-test/suite/rpl/t/rpl_row_trig001.test
share/mysql-test/suite/rpl/t/rpl_row_trig002.test
share/mysql-test/suite/rpl/t/rpl_row_trig003.test
share/mysql-test/suite/rpl/t/rpl_row_trig004.test
share/mysql-test/suite/rpl/t/rpl_row_trunc_temp.test
share/mysql-test/suite/rpl/t/rpl_row_unsafe_funcs.test
share/mysql-test/suite/rpl/t/rpl_row_until.test
share/mysql-test/suite/rpl/t/rpl_row_view01.test
share/mysql-test/suite/rpl/t/rpl_row_wide_table.test
share/mysql-test/suite/rpl/t/rpl_server_id1.test
share/mysql-test/suite/rpl/t/rpl_server_id2-slave.opt
share/mysql-test/suite/rpl/t/rpl_server_id2.test
share/mysql-test/suite/rpl/t/rpl_session_var.test
share/mysql-test/suite/rpl/t/rpl_set_charset.test
share/mysql-test/suite/rpl/t/rpl_set_null_innodb.test
share/mysql-test/suite/rpl/t/rpl_set_null_myisam.test
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/suite/rpl/t/rpl_show_slave_running.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_skip_error-slave.opt
share/mysql-test/suite/rpl/t/rpl_skip_error.test
share/mysql-test/suite/rpl/t/rpl_slave_grp_exec.test
share/mysql-test/suite/rpl/t/rpl_slave_load_in.test
share/mysql-test/suite/rpl/t/rpl_slave_load_remove_tmpfile-slave.opt
share/mysql-test/suite/rpl/t/rpl_slave_load_remove_tmpfile.test
Update mysql51-{client,server} package to 5.1.54. Functionality added or changed: * Support for the IBMDB2I storage engine has been removed. (Bug#58079) * The pstack library was nonfunctional and has been removed, along with the --with-pstack option for configure. The --enable-pstack option for mysqld is deprecated and will be removed in MySQL 5.5. (Bug#57210) Bugs fixed: * Performance: InnoDB Storage Engine: Improved concurrency when several ANALYZE TABLE or SHOW TABLE STATUS statements are run simultaneously for InnoDB tables. (Bug#53046) * InnoDB Storage Engine: For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#57799) * Partitioning: An INSERT ... ON DUPLICATE KEY UPDATE column = 0 statement on an AUTO_INCREMENT column caused the debug server to crash. (Bug#57890) * Several compilation problems were fixed. (Bug#57992, Bug#57993, Bug#57994, Bug#57995, Bug#57996, Bug#57997, Bug#58057) * Passing a string that was not null-terminated to UpdateXML() or ExtractValue() caused the server to fail with an assertion. (Bug#57279) * Queries executed using the Index Merge access method and a temporary file could return incorrect results. (Bug#56862) * The find_files() function used by SHOW statements performed redundant and unnecessary memory allocation. (Bug#51208)
2010-12-16 04:42:49 +01:00
share/mysql-test/suite/rpl/t/rpl_slave_load_tmpdir_not_exist-master.opt
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_slave_load_tmpdir_not_exist-slave.opt
share/mysql-test/suite/rpl/t/rpl_slave_load_tmpdir_not_exist.test
share/mysql-test/suite/rpl/t/rpl_slave_skip.test
share/mysql-test/suite/rpl/t/rpl_slave_status.test
Update mysql51-client/mysql51-server package to 5.1.45. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html Added a patch for recent security problem to mysql51-server, too. http://secunia.com/advisories/39454
2010-04-21 00:58:10 +02:00
share/mysql-test/suite/rpl/t/rpl_slow_query_log-slave.opt
share/mysql-test/suite/rpl/t/rpl_slow_query_log.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_sp-master.opt
share/mysql-test/suite/rpl/t/rpl_sp-slave.opt
share/mysql-test/suite/rpl/t/rpl_sp.test
share/mysql-test/suite/rpl/t/rpl_sp004.test
share/mysql-test/suite/rpl/t/rpl_sp_effects-master.opt
share/mysql-test/suite/rpl/t/rpl_sp_effects-slave.opt
share/mysql-test/suite/rpl/t/rpl_sp_effects.test
share/mysql-test/suite/rpl/t/rpl_sporadic_master-master.opt
share/mysql-test/suite/rpl/t/rpl_sporadic_master.test
share/mysql-test/suite/rpl/t/rpl_ssl.test
share/mysql-test/suite/rpl/t/rpl_ssl1.test
share/mysql-test/suite/rpl/t/rpl_start_stop_slave-slave.opt
share/mysql-test/suite/rpl/t/rpl_start_stop_slave.test
share/mysql-test/suite/rpl/t/rpl_stm_000001.test
share/mysql-test/suite/rpl/t/rpl_stm_EE_err2.test
share/mysql-test/suite/rpl/t/rpl_stm_auto_increment_bug33029.test
share/mysql-test/suite/rpl/t/rpl_stm_binlog_direct-master.opt
share/mysql-test/suite/rpl/t/rpl_stm_binlog_direct.test
share/mysql-test/suite/rpl/t/rpl_stm_conflicts.test
Update mysql51-{client,server} package to 5.1.51, MySQL 5.1.51. For full changes, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html Here is summary for security fixes: * Security Fix: During evaluation of arguments to extreme-value functions (such as LEAST() and GREATEST()), type errors did not propagate properly, causing the server to crash. (Bug#55826) * Security Fix: The server could crash after materializing a derived table that required a temporary table for grouping. (Bug#55568) * Security Fix: A user-variable assignment expression that is evaluated in a logical expression context can be precalculated in a temporary table for GROUP BY. However, when the expression value is used after creation of the temporary table, it was re-evaluated, not read from the table and a server crash resulted. (Bug#55564) * Security Fix: Pre-evaluation of LIKE predicates during view preparation could cause a server crash. (Bug#54568) * Security Fix: GROUP_CONCAT() and WITH ROLLUP together could cause a server crash. (Bug#54476) * Security Fix: Queries could cause a server crash if the GREATEST() or LEAST() function had a mixed list of numeric and LONGBLOB arguments, and the result of such a function was processed using an intermediate temporary table. (Bug#54461) * Security Fix: Queries with nested joins could cause an infinite loop in the server when used from stored procedures and prepared statements. (Bug#53544) * Security Fix: The PolyFromWKB() function could crash the server when improper WKB data was passed to the function. (Bug#51875)
2010-10-06 14:37:58 +02:00
share/mysql-test/suite/rpl/t/rpl_stm_create_if_not_exists.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_stm_flsh_tbls.test
share/mysql-test/suite/rpl/t/rpl_stm_insert_delayed.test
share/mysql-test/suite/rpl/t/rpl_stm_loadfile.test
share/mysql-test/suite/rpl/t/rpl_stm_log-master.opt
share/mysql-test/suite/rpl/t/rpl_stm_log-slave.opt
share/mysql-test/suite/rpl/t/rpl_stm_log.test
share/mysql-test/suite/rpl/t/rpl_stm_max_relay_size.test
share/mysql-test/suite/rpl/t/rpl_stm_mixing_engines.test
share/mysql-test/suite/rpl/t/rpl_stm_multi_query.test
share/mysql-test/suite/rpl/t/rpl_stm_no_op.test
Update mysql51-{client,server} to 5.1.63 (MySQL 5.1.63). Changes (http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html): * Security Fix: Bug #64884 was fixed. * Security Fix: Bug #59387 was fixed. * InnoDB: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. (Bug #13847885) * InnoDB: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. (Bug #12861864, Bug #11766019) * InnoDB: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. (Bug #11766634, Bug #59783) * Partitioning: After updating a row of a partitioned table and selecting that row within the same transaction with the query cache enabled, then performing a ROLLBACK, the same result was returned by an identical SELECT issued in a new transaction. (Bug #11761296, Bug #53775) * Replication: The --relay-log-space-limit option was sometimes ignored. More specifically, when the SQL thread went to sleep, it allowed the I/O thread to queue additional events in such a way that the relay log space limit was bypassed, and the number of events in the queue could grow well past the point where the relay logs needed to be rotated. Now in such cases, the SQL thread checks to see whether the I/O thread should rotate and provide the SQL thread a chance to purge the logs (thus freeing space). Note that, when the SQL thread is in the middle of a transaction, it cannot purge the logs; it can only ask for more events until the transaction is complete. Once the transaction is finished, the SQL thread can immediately instruct the I/O thread to rotate. (Bug #12400313, Bug #64503) References: See also Bug #13806492. * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored procedures on slave servers could cause replication failures. (Bug #12601974) * If the system time was adjusted backward during query execution, the apparent execution time could be negative. But in some cases these queries would be written to the slow query log, with the negative execution time written as a large unsigned number. Now statements with apparent negative execution time are not written to the slow query log. (Bug #63524, Bug #13454045) References: See also Bug #27208. * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * SHOW statements treated stored procedure, stored function, and event names as case sensitive. (Bug #56224, Bug #11763507) * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 14:59:39 +02:00
share/mysql-test/suite/rpl/t/rpl_stm_relay_ign_space-slave.opt
share/mysql-test/suite/rpl/t/rpl_stm_relay_ign_space.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_stm_reset_slave.test
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/suite/rpl/t/rpl_stm_sql_mode.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_stm_until.test
Update mysql51-{client,server} to 5.1.53. Most changes are related to replication and seems to no security fix. For more detail, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html
2010-11-26 14:52:58 +01:00
share/mysql-test/suite/rpl/t/rpl_stop_slave.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_switch_stm_row_mixed.test
share/mysql-test/suite/rpl/t/rpl_temp_table.test
share/mysql-test/suite/rpl/t/rpl_temp_table_mix_row.test
share/mysql-test/suite/rpl/t/rpl_temporary.test
share/mysql-test/suite/rpl/t/rpl_temporary_errors-slave.opt
share/mysql-test/suite/rpl/t/rpl_temporary_errors.test
Update mysql51-{client,server} package to 5.1.55. Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2011-02-13 17:19:45 +01:00
share/mysql-test/suite/rpl/t/rpl_test_framework.cnf
share/mysql-test/suite/rpl/t/rpl_test_framework.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_timezone-master.opt
share/mysql-test/suite/rpl/t/rpl_timezone-slave.opt
share/mysql-test/suite/rpl/t/rpl_timezone.test
share/mysql-test/suite/rpl/t/rpl_tmp_table_and_DDL.test
share/mysql-test/suite/rpl/t/rpl_trigger.test
share/mysql-test/suite/rpl/t/rpl_trunc_temp.test
share/mysql-test/suite/rpl/t/rpl_truncate_2myisam.test
share/mysql-test/suite/rpl/t/rpl_truncate_3innodb.test
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/suite/rpl/t/rpl_typeconv-slave.opt
share/mysql-test/suite/rpl/t/rpl_typeconv_innodb.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl/t/rpl_udf-master.opt
share/mysql-test/suite/rpl/t/rpl_udf-slave.opt
share/mysql-test/suite/rpl/t/rpl_udf.test
share/mysql-test/suite/rpl/t/rpl_user.test
share/mysql-test/suite/rpl/t/rpl_user_variables.test
share/mysql-test/suite/rpl/t/rpl_variables.test
share/mysql-test/suite/rpl/t/rpl_variables_stm.test
share/mysql-test/suite/rpl/t/rpl_view.test
share/mysql-test/suite/rpl_ndb/my.cnf
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_2innodb.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_2myisam.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_2ndb.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_2other.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_UUID.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_apply_status.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_auto_inc.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_bank.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_basic.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_blob.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_blob2.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_circular.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_circular_2ch.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_circular_simplex.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_commit_afterflush.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_ctype_ucs2_def.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_dd_basic.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_dd_partitions.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_ddl.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_delete_nowhere.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_do_db.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_do_table.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_extraCol.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_func003.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_idempotent.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_innodb2ndb.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_innodb_trans.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_insert_ignore.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_load.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_log.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_mixed_engines_transactions.result
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_mixed_tables.result
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_multi.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_multi_update2.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_multi_update3.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_myisam2ndb.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_relayrotate.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_rep_ignore.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_row_001.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_set_null.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_sp003.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_sp006.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_stm_innodb.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_sync.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndb_trig004.result
share/mysql-test/suite/rpl_ndb/r/rpl_ndbapi_multi.result
share/mysql-test/suite/rpl_ndb/r/rpl_row_basic_7ndb.result
share/mysql-test/suite/rpl_ndb/r/rpl_truncate_7ndb.result
share/mysql-test/suite/rpl_ndb/r/rpl_truncate_7ndb_2.result
share/mysql-test/suite/rpl_ndb/t/disabled.def
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_2innodb-master.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_2innodb-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_2innodb.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_2myisam-master.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_2myisam-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_2myisam.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_2ndb-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_2ndb.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_2other-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_2other.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_UUID.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_apply_status-master.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_apply_status.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_auto_inc.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_bank.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_basic.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_blob.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_blob2.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_circular.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_circular_2ch.cnf
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_circular_2ch.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_circular_simplex.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_commit_afterflush.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_ctype_ucs2_def-master.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_ctype_ucs2_def.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_dd_basic.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_dd_partitions-master.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_dd_partitions-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_dd_partitions.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_ddl.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_delete_nowhere.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_do_db-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_do_db.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_do_table-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_do_table.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_extraCol.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_func003.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_idempotent.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_innodb2ndb-master.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_innodb2ndb-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_innodb2ndb.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_innodb_trans-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_innodb_trans.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_insert_ignore.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_load.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_log-master.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_log.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_mixed_engines_transactions-master.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_mixed_engines_transactions-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_mixed_engines_transactions.test
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_mixed_tables-master.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_mixed_tables-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_mixed_tables.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_multi.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_multi_update2-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_multi_update2.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_multi_update3.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_myisam2ndb-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_myisam2ndb.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_relayrotate-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_relayrotate.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_rep_ignore-slave.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_rep_ignore.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_row_001.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_set_null.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_sp003.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_sp006.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_stm_innodb-master.opt
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_stm_innodb.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_sync.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndb_trig004.test
share/mysql-test/suite/rpl_ndb/t/rpl_ndbapi_multi.test
share/mysql-test/suite/rpl_ndb/t/rpl_row_basic_7ndb.test
share/mysql-test/suite/rpl_ndb/t/rpl_truncate_7ndb.test
share/mysql-test/suite/rpl_ndb/t/rpl_truncate_7ndb_2-master.opt
share/mysql-test/suite/rpl_ndb/t/rpl_truncate_7ndb_2.test
share/mysql-test/suite/stress/include/ddl.cln
share/mysql-test/suite/stress/include/ddl.pre
share/mysql-test/suite/stress/include/ddl1.inc
share/mysql-test/suite/stress/include/ddl2.inc
share/mysql-test/suite/stress/include/ddl3.inc
share/mysql-test/suite/stress/include/ddl4.inc
share/mysql-test/suite/stress/include/ddl5.inc
share/mysql-test/suite/stress/include/ddl6.inc
share/mysql-test/suite/stress/include/ddl7.inc
share/mysql-test/suite/stress/include/ddl8.inc
share/mysql-test/suite/stress/r/ddl_archive.result
share/mysql-test/suite/stress/r/ddl_csv.result
share/mysql-test/suite/stress/r/ddl_innodb.result
share/mysql-test/suite/stress/r/ddl_memory.result
share/mysql-test/suite/stress/r/ddl_myisam.result
share/mysql-test/suite/stress/r/ddl_ndb.result
share/mysql-test/suite/stress/t/ddl_archive.test
share/mysql-test/suite/stress/t/ddl_csv.test
share/mysql-test/suite/stress/t/ddl_innodb.test
share/mysql-test/suite/stress/t/ddl_memory.test
share/mysql-test/suite/stress/t/ddl_myisam.test
share/mysql-test/suite/stress/t/ddl_ndb.test
share/mysql-test/t/1st.test
share/mysql-test/t/alias.test
share/mysql-test/t/almost_full.test
share/mysql-test/t/alter_table-big.test
share/mysql-test/t/alter_table.test
share/mysql-test/t/analyse.test
share/mysql-test/t/analyze.test
share/mysql-test/t/ansi.test
share/mysql-test/t/archive-big.test
share/mysql-test/t/archive.test
share/mysql-test/t/archive_bitfield.test
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/t/archive_debug.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/archive_gis.test
share/mysql-test/t/auto_increment.test
share/mysql-test/t/backup-master.sh
share/mysql-test/t/backup.test
share/mysql-test/t/bench_count_distinct.test
share/mysql-test/t/bigint.test
share/mysql-test/t/binary.test
share/mysql-test/t/bool.test
share/mysql-test/t/bootstrap.test
Update mysql51-client/mysql51-server package to 5.1.45. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html Added a patch for recent security problem to mysql51-server, too. http://secunia.com/advisories/39454
2010-04-21 00:58:10 +02:00
share/mysql-test/t/bug39022.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/bug46080-master.opt
share/mysql-test/t/bug46080.test
Update mysql51-{client,server} package to 5.1.47. For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 03:52:21 +02:00
share/mysql-test/t/bug46261-master.opt
share/mysql-test/t/bug46261.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/bug46760-master.opt
share/mysql-test/t/bug46760.test
share/mysql-test/t/bug47671-master.opt
share/mysql-test/t/bug47671.test
share/mysql-test/t/bulk_replace.test
share/mysql-test/t/cache_innodb.test
share/mysql-test/t/case.test
share/mysql-test/t/cast.test
share/mysql-test/t/change_user-master.opt
share/mysql-test/t/change_user.test
share/mysql-test/t/check.test
share/mysql-test/t/client_xml.test
share/mysql-test/t/comments.test
share/mysql-test/t/commit_1innodb.test
share/mysql-test/t/compare.test
share/mysql-test/t/compress.test
share/mysql-test/t/concurrent_innodb_safelog-master.opt
share/mysql-test/t/concurrent_innodb_safelog.test
share/mysql-test/t/concurrent_innodb_unsafelog-master.opt
share/mysql-test/t/concurrent_innodb_unsafelog.test
share/mysql-test/t/connect.test
share/mysql-test/t/consistent_snapshot.test
share/mysql-test/t/constraints.test
share/mysql-test/t/contributors.test
share/mysql-test/t/count_distinct.test
share/mysql-test/t/count_distinct2-master.opt
share/mysql-test/t/count_distinct2.test
share/mysql-test/t/count_distinct3.test
share/mysql-test/t/crash_commit_before-master.opt
share/mysql-test/t/crash_commit_before.test
share/mysql-test/t/create-big.test
share/mysql-test/t/create.test
share/mysql-test/t/create_not_windows.test
share/mysql-test/t/create_select_tmp.test
share/mysql-test/t/csv.test
share/mysql-test/t/csv_alter_table.test
share/mysql-test/t/csv_not_null.test
share/mysql-test/t/ctype_ascii.test
share/mysql-test/t/ctype_big5.test
share/mysql-test/t/ctype_collate.test
share/mysql-test/t/ctype_cp1250_ch.test
share/mysql-test/t/ctype_cp1251.test
share/mysql-test/t/ctype_cp932_binlog_row.test
share/mysql-test/t/ctype_cp932_binlog_stm.test
share/mysql-test/t/ctype_create.test
share/mysql-test/t/ctype_eucjpms.test
share/mysql-test/t/ctype_euckr.test
share/mysql-test/t/ctype_filename.test
share/mysql-test/t/ctype_filesystem-master.opt
share/mysql-test/t/ctype_filesystem.test
share/mysql-test/t/ctype_gb2312.test
share/mysql-test/t/ctype_gbk.test
share/mysql-test/t/ctype_gbk_binlog.test
share/mysql-test/t/ctype_hebrew.test
share/mysql-test/t/ctype_latin1.test
share/mysql-test/t/ctype_latin1_de-master.opt
share/mysql-test/t/ctype_latin1_de.test
share/mysql-test/t/ctype_latin2.test
share/mysql-test/t/ctype_latin2_ch.test
share/mysql-test/t/ctype_ldml-master.opt
share/mysql-test/t/ctype_ldml.test
share/mysql-test/t/ctype_many.test
share/mysql-test/t/ctype_mb.test
share/mysql-test/t/ctype_recoding.test
share/mysql-test/t/ctype_sjis.test
share/mysql-test/t/ctype_tis620.test
share/mysql-test/t/ctype_uca.test
share/mysql-test/t/ctype_ucs.test
share/mysql-test/t/ctype_ucs2_def-master.opt
share/mysql-test/t/ctype_ucs2_def.test
share/mysql-test/t/ctype_ujis.test
share/mysql-test/t/ctype_ujis_ucs2.test
share/mysql-test/t/ctype_utf8.test
share/mysql-test/t/date_formats-master.opt
share/mysql-test/t/date_formats.test
share/mysql-test/t/ddl_i18n_koi8r.test
share/mysql-test/t/ddl_i18n_utf8.test
share/mysql-test/t/deadlock_innodb.test
share/mysql-test/t/debug_sync.test
share/mysql-test/t/default.test
share/mysql-test/t/delayed.test
share/mysql-test/t/delete.test
share/mysql-test/t/derived.test
share/mysql-test/t/dirty_close.test
share/mysql-test/t/disabled.def
share/mysql-test/t/distinct.test
share/mysql-test/t/drop.test
share/mysql-test/t/empty_table.test
share/mysql-test/t/endspace.test
share/mysql-test/t/error_simulation.test
share/mysql-test/t/errors.test
share/mysql-test/t/events_1.test
share/mysql-test/t/events_2.test
share/mysql-test/t/events_bugs-master.opt
share/mysql-test/t/events_bugs.test
share/mysql-test/t/events_embedded.test
share/mysql-test/t/events_grant.test
share/mysql-test/t/events_logs_tests-master.opt
share/mysql-test/t/events_logs_tests.test
share/mysql-test/t/events_microsec.test
share/mysql-test/t/events_restart-master.opt
share/mysql-test/t/events_restart.test
share/mysql-test/t/events_scheduling.test
share/mysql-test/t/events_stress.test
share/mysql-test/t/events_time_zone.test
share/mysql-test/t/events_trans.test
share/mysql-test/t/events_trans_notembedded.test
share/mysql-test/t/exampledb.test
share/mysql-test/t/execution_constants.test
share/mysql-test/t/explain.test
share/mysql-test/t/fix_priv_tables.test
share/mysql-test/t/flush.test
share/mysql-test/t/flush2-master.opt
share/mysql-test/t/flush2.test
share/mysql-test/t/flush_block_commit.test
share/mysql-test/t/flush_block_commit_notembedded.test
share/mysql-test/t/flush_read_lock_kill-master.opt
share/mysql-test/t/flush_read_lock_kill.test
share/mysql-test/t/flush_table.test
share/mysql-test/t/foreign_key.test
share/mysql-test/t/fulltext.test
share/mysql-test/t/fulltext2.test
share/mysql-test/t/fulltext3.test
share/mysql-test/t/fulltext_cache.test
share/mysql-test/t/fulltext_distinct.test
share/mysql-test/t/fulltext_left_join.test
share/mysql-test/t/fulltext_multi.test
share/mysql-test/t/fulltext_order_by.test
share/mysql-test/t/fulltext_plugin-master.opt
share/mysql-test/t/fulltext_plugin.test
share/mysql-test/t/fulltext_update.test
share/mysql-test/t/fulltext_var.test
share/mysql-test/t/func_compress.test
share/mysql-test/t/func_concat.test
share/mysql-test/t/func_crypt.test
share/mysql-test/t/func_date_add.test
share/mysql-test/t/func_default.test
share/mysql-test/t/func_des_encrypt.test
share/mysql-test/t/func_encrypt-master.opt
share/mysql-test/t/func_encrypt.test
share/mysql-test/t/func_encrypt_nossl.test
Update mysql51-{client,server} package to 5.1.57. This is simply maintenance release, no security fix. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-57.html in detail.
2011-05-08 18:01:57 +02:00
share/mysql-test/t/func_encrypt_ucs2.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/func_equal.test
share/mysql-test/t/func_gconcat.test
share/mysql-test/t/func_group.test
share/mysql-test/t/func_group_innodb.test
share/mysql-test/t/func_if.test
share/mysql-test/t/func_in.test
share/mysql-test/t/func_isnull.test
share/mysql-test/t/func_like.test
share/mysql-test/t/func_math.test
share/mysql-test/t/func_misc.test
share/mysql-test/t/func_op.test
share/mysql-test/t/func_regexp.test
share/mysql-test/t/func_rollback.test
share/mysql-test/t/func_sapdb.test
share/mysql-test/t/func_set.test
share/mysql-test/t/func_str.test
share/mysql-test/t/func_system.test
share/mysql-test/t/func_test.test
share/mysql-test/t/func_time.test
share/mysql-test/t/func_timestamp.test
share/mysql-test/t/gcc296.test
share/mysql-test/t/gis-rtree.test
share/mysql-test/t/gis.test
share/mysql-test/t/grant.test
share/mysql-test/t/grant2.test
share/mysql-test/t/grant3-master.opt
share/mysql-test/t/grant3.test
share/mysql-test/t/grant_cache_no_prot.test
share/mysql-test/t/grant_cache_ps_prot.test
share/mysql-test/t/grant_lowercase_fs.test
share/mysql-test/t/greedy_optimizer.test
share/mysql-test/t/group_by.test
share/mysql-test/t/group_min_max.test
share/mysql-test/t/group_min_max_innodb.test
share/mysql-test/t/handler_innodb.test
share/mysql-test/t/handler_myisam.test
share/mysql-test/t/having.test
share/mysql-test/t/heap.test
share/mysql-test/t/heap_auto_increment.test
share/mysql-test/t/heap_btree.test
share/mysql-test/t/heap_hash.test
share/mysql-test/t/help.test
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/t/implicit_char_to_num_conversion.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/index_merge_innodb.test
share/mysql-test/t/index_merge_myisam.test
share/mysql-test/t/information_schema.test
share/mysql-test/t/information_schema_chmod.test
share/mysql-test/t/information_schema_db.test
share/mysql-test/t/information_schema_inno.test
share/mysql-test/t/information_schema_part.test
share/mysql-test/t/init_connect-master.opt
share/mysql-test/t/init_connect.test
share/mysql-test/t/init_file-master.opt
share/mysql-test/t/init_file.test
share/mysql-test/t/innodb_ignore_builtin-master.opt
share/mysql-test/t/innodb_ignore_builtin.test
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/t/innodb_mysql_lock2.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/insert.test
share/mysql-test/t/insert_notembedded.test
share/mysql-test/t/insert_select.test
share/mysql-test/t/insert_update.test
share/mysql-test/t/join.test
share/mysql-test/t/join_crash.test
share/mysql-test/t/join_nested.test
share/mysql-test/t/join_outer.test
share/mysql-test/t/join_outer_innodb.test
share/mysql-test/t/key.test
share/mysql-test/t/key_cache-master.opt
share/mysql-test/t/key_cache.test
share/mysql-test/t/key_diff.test
share/mysql-test/t/key_primary.test
share/mysql-test/t/keywords.test
share/mysql-test/t/kill.test
share/mysql-test/t/limit.test
share/mysql-test/t/loaddata.test
share/mysql-test/t/loaddata_autocom_innodb.test
share/mysql-test/t/locale.test
share/mysql-test/t/lock.test
share/mysql-test/t/lock_multi.test
share/mysql-test/t/lock_multi_bug38499.test
share/mysql-test/t/lock_multi_bug38691.test
Update mysql51-{client,server} package to 5.1.48. Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-07-05 05:15:04 +02:00
share/mysql-test/t/lock_sync.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/lock_tables_lost_commit-master.opt
share/mysql-test/t/lock_tables_lost_commit.test
share/mysql-test/t/log_state-master.opt
share/mysql-test/t/log_state.test
share/mysql-test/t/log_tables-big-master.opt
share/mysql-test/t/log_tables-big.test
share/mysql-test/t/log_tables-master.opt
share/mysql-test/t/log_tables.test
share/mysql-test/t/log_tables_debug.test
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/t/log_tables_upgrade.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/long_tmpdir-master.opt
share/mysql-test/t/long_tmpdir-master.sh
share/mysql-test/t/long_tmpdir.test
share/mysql-test/t/lowercase_fs_off.test
share/mysql-test/t/lowercase_mixed_tmpdir-master.opt
share/mysql-test/t/lowercase_mixed_tmpdir-master.sh
share/mysql-test/t/lowercase_mixed_tmpdir.test
share/mysql-test/t/lowercase_mixed_tmpdir_innodb-master.opt
share/mysql-test/t/lowercase_mixed_tmpdir_innodb-master.sh
share/mysql-test/t/lowercase_mixed_tmpdir_innodb.test
share/mysql-test/t/lowercase_table-master.opt
share/mysql-test/t/lowercase_table.test
share/mysql-test/t/lowercase_table2.test
share/mysql-test/t/lowercase_table3-master.opt
share/mysql-test/t/lowercase_table3.test
Update mysql51-{client,server} to 5.1.53. Most changes are related to replication and seems to no security fix. For more detail, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html
2010-11-26 14:52:58 +01:00
share/mysql-test/t/lowercase_table4-master.opt
share/mysql-test/t/lowercase_table4.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/lowercase_table_grant-master.opt
share/mysql-test/t/lowercase_table_grant.test
share/mysql-test/t/lowercase_table_qcache-master.opt
share/mysql-test/t/lowercase_table_qcache.test
share/mysql-test/t/lowercase_utf8-master.opt
share/mysql-test/t/lowercase_utf8.test
share/mysql-test/t/lowercase_view-master.opt
share/mysql-test/t/lowercase_view.test
share/mysql-test/t/merge-big.test
share/mysql-test/t/merge.test
share/mysql-test/t/merge_innodb.test
share/mysql-test/t/metadata.test
share/mysql-test/t/mix2_myisam.test
share/mysql-test/t/mix2_myisam_ucs2.test
share/mysql-test/t/multi_statement-master.opt
share/mysql-test/t/multi_statement.test
share/mysql-test/t/multi_update-master.opt
share/mysql-test/t/multi_update.test
share/mysql-test/t/multi_update2-master.opt
share/mysql-test/t/multi_update2.test
share/mysql-test/t/multi_update_tiny_hash-master.opt
share/mysql-test/t/multi_update_tiny_hash.test
share/mysql-test/t/myisam-blob-master.opt
share/mysql-test/t/myisam-blob.test
share/mysql-test/t/myisam-system.test
share/mysql-test/t/myisam.test
share/mysql-test/t/myisam_crash_before_flush_keys-master.opt
share/mysql-test/t/myisam_crash_before_flush_keys.test
share/mysql-test/t/myisam_debug.test
share/mysql-test/t/myisampack.test
share/mysql-test/t/mysql-bug41486.test
share/mysql-test/t/mysql-bug45236.test
share/mysql-test/t/mysql.test
share/mysql-test/t/mysql_client_test-master.opt
share/mysql-test/t/mysql_client_test.test
share/mysql-test/t/mysql_comments.sql
share/mysql-test/t/mysql_comments.test
share/mysql-test/t/mysql_cp932.test
share/mysql-test/t/mysql_delimiter.sql
share/mysql-test/t/mysql_delimiter_19799.sql
share/mysql-test/t/mysql_delimiter_source.sql
share/mysql-test/t/mysql_protocols.test
share/mysql-test/t/mysql_upgrade.test
share/mysql-test/t/mysqladmin.test
share/mysql-test/t/mysqlbinlog-master.opt
share/mysql-test/t/mysqlbinlog.test
share/mysql-test/t/mysqlbinlog_row_big.test
share/mysql-test/t/mysqlcheck.test
share/mysql-test/t/mysqldump-compat.opt
share/mysql-test/t/mysqldump-compat.test
share/mysql-test/t/mysqldump-max.test
share/mysql-test/t/mysqldump-no-binlog-master.opt
share/mysql-test/t/mysqldump-no-binlog.test
share/mysql-test/t/mysqldump.test
share/mysql-test/t/mysqldump_restore.test
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
share/mysql-test/t/mysqlhotcopy_archive.test
share/mysql-test/t/mysqlhotcopy_myisam.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/mysqlshow.test
share/mysql-test/t/mysqlslap.test
share/mysql-test/t/mysqltest.test
share/mysql-test/t/named_pipe-master.opt
share/mysql-test/t/named_pipe.test
share/mysql-test/t/negation_elimination.test
share/mysql-test/t/no-threads-master.opt
share/mysql-test/t/no-threads.test
Update mysql51-client/mysql51-server package to 5.1.45. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html Added a patch for recent security problem to mysql51-server, too. http://secunia.com/advisories/39454
2010-04-21 00:58:10 +02:00
share/mysql-test/t/no_binlog.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/not_embedded_server-master.opt
share/mysql-test/t/not_embedded_server.test
share/mysql-test/t/not_partition.test
share/mysql-test/t/null.test
share/mysql-test/t/null_key.test
share/mysql-test/t/odbc.test
share/mysql-test/t/olap.test
share/mysql-test/t/openssl_1.test
share/mysql-test/t/order_by.test
share/mysql-test/t/order_fill_sortbuf-master.opt
share/mysql-test/t/order_fill_sortbuf.test
share/mysql-test/t/outfile.test
share/mysql-test/t/outfile_loaddata.test
share/mysql-test/t/overflow.test
share/mysql-test/t/packet.test
share/mysql-test/t/parser.test
share/mysql-test/t/parser_bug21114_innodb.test
share/mysql-test/t/parser_not_embedded.test
share/mysql-test/t/parser_precedence.test
share/mysql-test/t/parser_stack.test
share/mysql-test/t/partition-master.opt
share/mysql-test/t/partition.test
share/mysql-test/t/partition_archive.test
Update mysql51-{client,server} package from 5.1.51 to 5.1.52. This is maintainous release and pleare refer in detail: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html One note from the changes: * Security Fix: In prepared-statement mode, EXPLAIN for a SELECT from a derived table caused a server crash. (Bug#54488)
2010-11-04 16:57:07 +01:00
share/mysql-test/t/partition_binlog_stmt.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/partition_blackhole.test
share/mysql-test/t/partition_bug18198.test
Update mysql51-{client,server} to 5.1.63 (MySQL 5.1.63). Changes (http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html): * Security Fix: Bug #64884 was fixed. * Security Fix: Bug #59387 was fixed. * InnoDB: Deleting a huge amount of data from InnoDB tables within a short time could cause the purge operation that flushes data from the buffer pool to stall. If this issue occurs, restart the server to work around it. This issue is only likely to occur on 32-bit platforms. (Bug #13847885) * InnoDB: If the server crashed during a TRUNCATE TABLE or CREATE INDEX statement for an InnoDB table, or a DROP DATABASE statement for a database containing InnoDB tables, an index could be corrupted, causing an error message when accessing the table after restart: InnoDB: Error: trying to load index index_name for table table_name InnoDB: but the index tree has been freed! In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the built-in InnoDB storage engine. (Bug #12861864, Bug #11766019) * InnoDB: When data was removed from an InnoDB table, newly inserted data might not reuse the freed disk blocks, leading to an unexpected size increase for the system tablespace or .ibd file (depending on the setting of innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd file in some cases but not others. The freed disk blocks would eventually be reused as additional data was inserted. (Bug #11766634, Bug #59783) * Partitioning: After updating a row of a partitioned table and selecting that row within the same transaction with the query cache enabled, then performing a ROLLBACK, the same result was returned by an identical SELECT issued in a new transaction. (Bug #11761296, Bug #53775) * Replication: The --relay-log-space-limit option was sometimes ignored. More specifically, when the SQL thread went to sleep, it allowed the I/O thread to queue additional events in such a way that the relay log space limit was bypassed, and the number of events in the queue could grow well past the point where the relay logs needed to be rotated. Now in such cases, the SQL thread checks to see whether the I/O thread should rotate and provide the SQL thread a chance to purge the logs (thus freeing space). Note that, when the SQL thread is in the middle of a transaction, it cannot purge the logs; it can only ask for more events until the transaction is complete. Once the transaction is finished, the SQL thread can immediately instruct the I/O thread to rotate. (Bug #12400313, Bug #64503) References: See also Bug #13806492. * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored procedures on slave servers could cause replication failures. (Bug #12601974) * If the system time was adjusted backward during query execution, the apparent execution time could be negative. But in some cases these queries would be written to the slow query log, with the negative execution time written as a large unsigned number. Now statements with apparent negative execution time are not written to the slow query log. (Bug #63524, Bug #13454045) References: See also Bug #27208. * mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way in libmysqld. (Bug #62136, Bug #13738989) References: See also Bug #47485. * SHOW statements treated stored procedure, stored function, and event names as case sensitive. (Bug #56224, Bug #11763507) * On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
2012-05-13 14:59:39 +02:00
share/mysql-test/t/partition_cache.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/partition_charset.test
share/mysql-test/t/partition_csv.test
share/mysql-test/t/partition_datatype.test
Update mysql51-client/mysql51-server package to 5.1.45. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html Added a patch for recent security problem to mysql51-server, too. http://secunia.com/advisories/39454
2010-04-21 00:58:10 +02:00
share/mysql-test/t/partition_debug_sync.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/partition_disabled-master.opt
share/mysql-test/t/partition_disabled.test
share/mysql-test/t/partition_error.test
share/mysql-test/t/partition_federated.test
share/mysql-test/t/partition_grant.test
share/mysql-test/t/partition_hash.test
share/mysql-test/t/partition_innodb-master.opt
share/mysql-test/t/partition_innodb.test
share/mysql-test/t/partition_innodb_builtin.test
share/mysql-test/t/partition_innodb_plugin.test
share/mysql-test/t/partition_innodb_semi_consistent-master.opt
share/mysql-test/t/partition_innodb_semi_consistent.test
share/mysql-test/t/partition_innodb_stmt.test
share/mysql-test/t/partition_list.test
share/mysql-test/t/partition_mgm.test
share/mysql-test/t/partition_mgm_err.test
share/mysql-test/t/partition_mgm_err2.test
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/t/partition_myisam.test
Update mysql51-{client,server} package to 5.1.51, MySQL 5.1.51. For full changes, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html Here is summary for security fixes: * Security Fix: During evaluation of arguments to extreme-value functions (such as LEAST() and GREATEST()), type errors did not propagate properly, causing the server to crash. (Bug#55826) * Security Fix: The server could crash after materializing a derived table that required a temporary table for grouping. (Bug#55568) * Security Fix: A user-variable assignment expression that is evaluated in a logical expression context can be precalculated in a temporary table for GROUP BY. However, when the expression value is used after creation of the temporary table, it was re-evaluated, not read from the table and a server crash resulted. (Bug#55564) * Security Fix: Pre-evaluation of LIKE predicates during view preparation could cause a server crash. (Bug#54568) * Security Fix: GROUP_CONCAT() and WITH ROLLUP together could cause a server crash. (Bug#54476) * Security Fix: Queries could cause a server crash if the GREATEST() or LEAST() function had a mixed list of numeric and LONGBLOB arguments, and the result of such a function was processed using an intermediate temporary table. (Bug#54461) * Security Fix: Queries with nested joins could cause an infinite loop in the server when used from stored procedures and prepared statements. (Bug#53544) * Security Fix: The PolyFromWKB() function could crash the server when improper WKB data was passed to the function. (Bug#51875)
2010-10-06 14:37:58 +02:00
share/mysql-test/t/partition_not_blackhole-master.opt
share/mysql-test/t/partition_not_blackhole.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/partition_not_windows-master.opt
share/mysql-test/t/partition_not_windows.test
share/mysql-test/t/partition_open_files_limit-master.opt
share/mysql-test/t/partition_open_files_limit.test
share/mysql-test/t/partition_order.test
share/mysql-test/t/partition_pruning.test
share/mysql-test/t/partition_range.test
share/mysql-test/t/partition_rename_longfilename.test
share/mysql-test/t/partition_symlink.test
share/mysql-test/t/partition_windows.test
share/mysql-test/t/perror-win.test
share/mysql-test/t/perror.test
share/mysql-test/t/plugin-master.opt
share/mysql-test/t/plugin.test
share/mysql-test/t/plugin_load-master.opt
share/mysql-test/t/plugin_load.test
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/t/plugin_not_embedded-master.opt
share/mysql-test/t/plugin_not_embedded.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/preload.test
share/mysql-test/t/profiling.test
share/mysql-test/t/ps-master.opt
share/mysql-test/t/ps.test
share/mysql-test/t/ps_10nestset.test
share/mysql-test/t/ps_11bugs.test
share/mysql-test/t/ps_1general.test
share/mysql-test/t/ps_2myisam.test
share/mysql-test/t/ps_3innodb.test
share/mysql-test/t/ps_4heap.test
share/mysql-test/t/ps_5merge.test
share/mysql-test/t/ps_ddl.test
share/mysql-test/t/ps_ddl1.test
share/mysql-test/t/ps_grant.test
share/mysql-test/t/ps_not_windows.test
share/mysql-test/t/query_cache.test
share/mysql-test/t/query_cache_28249.test
share/mysql-test/t/query_cache_debug.test
share/mysql-test/t/query_cache_merge.test
share/mysql-test/t/query_cache_notembedded.test
share/mysql-test/t/query_cache_ps_no_prot.test
share/mysql-test/t/query_cache_ps_ps_prot.test
share/mysql-test/t/query_cache_with_views.test
share/mysql-test/t/range.test
share/mysql-test/t/read_many_rows_innodb.test
share/mysql-test/t/read_only.test
share/mysql-test/t/read_only_innodb.test
share/mysql-test/t/rename.test
share/mysql-test/t/renamedb.test
share/mysql-test/t/repair.test
share/mysql-test/t/replace.test
share/mysql-test/t/rollback.test
share/mysql-test/t/round.test
share/mysql-test/t/row.test
share/mysql-test/t/rowid_order_innodb.test
share/mysql-test/t/schema.test
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
share/mysql-test/t/secure_file_priv_win-master.opt
share/mysql-test/t/secure_file_priv_win.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/select.test
share/mysql-test/t/select_found.test
share/mysql-test/t/select_safe.test
share/mysql-test/t/shm-master.opt
share/mysql-test/t/shm.test
share/mysql-test/t/show_check-master.opt
share/mysql-test/t/show_check.test
share/mysql-test/t/skip_grants-master.opt
share/mysql-test/t/skip_grants.test
share/mysql-test/t/skip_log_bin-master.opt
share/mysql-test/t/skip_log_bin.test
share/mysql-test/t/skip_name_resolve-master.opt
share/mysql-test/t/skip_name_resolve.test
share/mysql-test/t/sp-big.test
share/mysql-test/t/sp-bugs.test
share/mysql-test/t/sp-code.test
share/mysql-test/t/sp-destruct.test
share/mysql-test/t/sp-dynamic.test
share/mysql-test/t/sp-error.test
share/mysql-test/t/sp-fib.test
share/mysql-test/t/sp-prelocking.test
share/mysql-test/t/sp-security.test
share/mysql-test/t/sp-threads.test
share/mysql-test/t/sp-ucs2.test
share/mysql-test/t/sp-vars.test
share/mysql-test/t/sp.test
share/mysql-test/t/sp_gis.test
share/mysql-test/t/sp_notembedded.test
share/mysql-test/t/sp_stress_case.test
share/mysql-test/t/sp_sync.test
share/mysql-test/t/sp_trans.test
share/mysql-test/t/sp_trans_log.test
share/mysql-test/t/sql_mode.test
share/mysql-test/t/ssl-big.test
share/mysql-test/t/ssl.test
Update mysql51-{client,server} to 5.1.50. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-50.html for full changes . InnoDB Notes: InnoDB Plugin has been upgraded to version 1.0.11. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), generic Linux RPM packages, and any builds produced with the icc compiler. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: Important Change: Replication: The LOAD DATA INFILE statement is now considered unsafe for statement-based replication. When using statement-based logging mode, the statement now produces a warning; when using mixed-format logging, the statement is made using the row-based format. (Bug#34283) Partitioning: UPDATE and INSERT statements affecting partitioned tables performed poorly when using row-based replication. (Bug#52517) Partitioning: INSERT ON DUPLICATE KEY UPDATE statements performed poorly on tables having many partitions. This was because the handler function for reading a row from a specific index was not optimized in the partitioning handler. (Bug#52455) The server could crash on shutdown, if started with --innodb-use-system-malloc=0. (Bug#55581) GROUP BY operations used max_sort_length inconsistently. (Bug#55188) Building MySQL on Solaris 8 x86 failed when using Sun Studio due to gcc inline assembler code. (Bug#55061) In debug builds, an assertion could be raised when the server tried to send an OK packet to the client after having failed to detect errors during processing of the WHERE condition of an UPDATE statement. (Bug#54734) The database server could crash when renaming a table that had active transactions. (This issue only affected the database server when built for debugging.) (Bug#54453) The server could crash during the recovery phase of startup, if it previously crashed while inserting BLOB or other large columns that use off-page storage into an InnoDB table created with ROW_FORMAT=REDUNDANT or ROW_FORMAT=COMPACT. (Bug#54408) For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#54358) A client could supply data in chunks to a prepared statement parameter other than of type TEXT or BLOB using the mysql_stmt_send_long_data() C API function (or COM_STMT_SEND_LONG_DATA command). This led to a crash because other data types are not valid for long data. (Bug#54041) mysql_secure_installation did not properly identify local accounts and could incorrectly remove nonlocal root accounts. (Bug#54004) Transactions could be incorrectly committed during recovery, rather than rolled back, if the server crashed and was restarted after performing ALTER TABLE...ADD PRIMARY KEY on an InnoDB table, or some other operation that involves copying the entire table. (Bug#53756) Portability problems in SHOW STATUS could lead to incorrect results on some platforms. (Bug#53493) Builds of MySQL generated a large number of warnings. (Bug#53445) With lower_case_table_names set to a nonzero value, searches for table or database names in INFORMATION_SCHEMA tables could produce incorrect results. (Bug#53095) The ABI check for MySQL failed to compile with gcc 4.5. (Bug#52514) mysql_secure_installation sometimes failed to locate the mysql client. (Bug#52274) Reading a ucs2 data file with LOAD DATA INFILE was subject to three problems. 1) Incorrect parsing of the file as ucs2 data, resulting in incorrect length of the parsed string. This is fixed by truncating the invalid trailing bytes (incomplete multibyte characters) when reading from the file. 2) Reads from a proper ucs2 file did not recognize newline characters. This is fixed by first checking whether a byte is a newline (or any other special character) before reading it as a part of a multibyte character. 3) When using user variables to hold column data, the character set of the user variable was set incorrectly to the database charset. This is fixed by setting it to the character set specified in the LOAD DATA INFILE statement, if any. (Bug#51876) Searches in INFORMATION_SCHEMA tables for rows matching a nonexistent database produced an error instead of an empty query result. (Bug#49542) On FreeBSD, memory mapping for MERGE tables could fail if underlying tables were empty. (Bug#47139) The my_like_range_xxx() functions returned badly formed maximum strings for Asian character sets, which caused problems for storage engines. (Bug#45012) A debugging assertion could be raised after a write failure to a closed socket. (Bug#42496) An assertion failure occurred within yaSSL for very long keys. (Bug#29784) See also Bug#53463.
2010-09-08 18:24:57 +02:00
share/mysql-test/t/ssl_8k_key-master.opt
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/ssl_8k_key.test
Update mysql51-{client,server} package to 5.1.57. This is simply maintenance release, no security fix. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-57.html in detail.
2011-05-08 18:01:57 +02:00
share/mysql-test/t/ssl_cipher-master.opt
share/mysql-test/t/ssl_cipher.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/ssl_compress.test
share/mysql-test/t/ssl_connect.test
share/mysql-test/t/status-master.opt
share/mysql-test/t/status.test
share/mysql-test/t/status2.test
share/mysql-test/t/strict.test
share/mysql-test/t/strict_autoinc_1myisam.test
share/mysql-test/t/strict_autoinc_2innodb.test
share/mysql-test/t/strict_autoinc_3heap.test
share/mysql-test/t/subselect.test
share/mysql-test/t/subselect2.test
share/mysql-test/t/subselect3.test
share/mysql-test/t/subselect4.test
share/mysql-test/t/subselect_debug.test
share/mysql-test/t/subselect_gis.test
share/mysql-test/t/subselect_innodb.test
share/mysql-test/t/subselect_notembedded.test
share/mysql-test/t/sum_distinct-big.test
share/mysql-test/t/sum_distinct.test
share/mysql-test/t/symlink.test
share/mysql-test/t/synchronization.test
share/mysql-test/t/sysdate_is_now-master.opt
share/mysql-test/t/sysdate_is_now.test
share/mysql-test/t/system_mysql_db.test
share/mysql-test/t/system_mysql_db_fix30020-master.opt
share/mysql-test/t/system_mysql_db_fix30020.test
share/mysql-test/t/system_mysql_db_fix40123-master.opt
share/mysql-test/t/system_mysql_db_fix40123.test
share/mysql-test/t/system_mysql_db_fix50030-master.opt
share/mysql-test/t/system_mysql_db_fix50030.test
share/mysql-test/t/system_mysql_db_fix50117-master.opt
share/mysql-test/t/system_mysql_db_fix50117.test
share/mysql-test/t/system_mysql_db_refs.test
share/mysql-test/t/tablelock.test
share/mysql-test/t/temp_table-master.opt
share/mysql-test/t/temp_table.test
share/mysql-test/t/timezone-master.opt
share/mysql-test/t/timezone.test
share/mysql-test/t/timezone2.test
share/mysql-test/t/timezone3-master.opt
share/mysql-test/t/timezone3.test
share/mysql-test/t/timezone4-master.opt
share/mysql-test/t/timezone4.test
share/mysql-test/t/timezone_grant.test
share/mysql-test/t/trigger-compat.test
share/mysql-test/t/trigger-trans.test
share/mysql-test/t/trigger.test
share/mysql-test/t/trigger_notembedded.test
share/mysql-test/t/truncate.test
share/mysql-test/t/type_binary.test
share/mysql-test/t/type_bit.test
share/mysql-test/t/type_bit_innodb.test
share/mysql-test/t/type_blob.test
share/mysql-test/t/type_date.test
share/mysql-test/t/type_datetime.test
share/mysql-test/t/type_decimal.test
share/mysql-test/t/type_enum.test
share/mysql-test/t/type_float.test
share/mysql-test/t/type_nchar.test
share/mysql-test/t/type_newdecimal-big.test
share/mysql-test/t/type_newdecimal.test
share/mysql-test/t/type_ranges.test
share/mysql-test/t/type_set.test
share/mysql-test/t/type_time.test
share/mysql-test/t/type_timestamp.test
share/mysql-test/t/type_uint.test
share/mysql-test/t/type_varchar.test
share/mysql-test/t/type_year.test
share/mysql-test/t/udf-master.opt
share/mysql-test/t/udf.test
share/mysql-test/t/udf_skip_grants-master.opt
share/mysql-test/t/udf_skip_grants.test
share/mysql-test/t/union-master.opt
share/mysql-test/t/union.test
share/mysql-test/t/unsafe_binlog_innodb-master.opt
share/mysql-test/t/unsafe_binlog_innodb.test
share/mysql-test/t/update.test
share/mysql-test/t/upgrade.test
share/mysql-test/t/user_limits.test
share/mysql-test/t/user_var-binlog.test
share/mysql-test/t/user_var.test
share/mysql-test/t/varbinary.test
share/mysql-test/t/variables-big.test
share/mysql-test/t/variables-notembedded-master.opt
share/mysql-test/t/variables-notembedded.test
share/mysql-test/t/variables.test
Update mysql51-client/mysql51-server package to 5.1.45. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html Added a patch for recent security problem to mysql51-server, too. http://secunia.com/advisories/39454
2010-04-21 00:58:10 +02:00
share/mysql-test/t/variables_community.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/variables_debug.test
share/mysql-test/t/view.test
Update mysql51-client/mysql51-server package to 5.1.46. This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 17:59:23 +02:00
share/mysql-test/t/view_alias.test
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
share/mysql-test/t/view_grant.test
share/mysql-test/t/wait_timeout.test
share/mysql-test/t/warnings-master.opt
share/mysql-test/t/warnings.test
share/mysql-test/t/warnings_engine_disabled-master.opt
share/mysql-test/t/warnings_engine_disabled.test
share/mysql-test/t/windows.test
share/mysql-test/t/xa.test
share/mysql-test/t/xml.test
share/mysql-test/valgrind.supp
share/mysql/charsets/Index.xml
share/mysql/charsets/README
share/mysql/charsets/armscii8.xml
share/mysql/charsets/ascii.xml
share/mysql/charsets/cp1250.xml
share/mysql/charsets/cp1251.xml
share/mysql/charsets/cp1256.xml
share/mysql/charsets/cp1257.xml
share/mysql/charsets/cp850.xml
share/mysql/charsets/cp852.xml
share/mysql/charsets/cp866.xml
share/mysql/charsets/dec8.xml
share/mysql/charsets/geostd8.xml
share/mysql/charsets/greek.xml
share/mysql/charsets/hebrew.xml
share/mysql/charsets/hp8.xml
share/mysql/charsets/keybcs2.xml
share/mysql/charsets/koi8r.xml
share/mysql/charsets/koi8u.xml
share/mysql/charsets/latin1.xml
share/mysql/charsets/latin2.xml
share/mysql/charsets/latin5.xml
share/mysql/charsets/latin7.xml
share/mysql/charsets/macce.xml
share/mysql/charsets/macroman.xml
share/mysql/charsets/swe7.xml
share/mysql/czech/errmsg.sys
share/mysql/danish/errmsg.sys
share/mysql/dutch/errmsg.sys
share/mysql/english/errmsg.sys
share/mysql/errmsg.txt
share/mysql/estonian/errmsg.sys
share/mysql/french/errmsg.sys
share/mysql/german/errmsg.sys
share/mysql/greek/errmsg.sys
share/mysql/hungarian/errmsg.sys
share/mysql/italian/errmsg.sys
share/mysql/japanese/errmsg.sys
share/mysql/korean/errmsg.sys
share/mysql/mi_test_all
share/mysql/mi_test_all.res
share/mysql/mysql.server
share/mysql/mysqld_multi.server
share/mysql/norwegian-ny/errmsg.sys
share/mysql/norwegian/errmsg.sys
share/mysql/polish/errmsg.sys
share/mysql/portuguese/errmsg.sys
share/mysql/romanian/errmsg.sys
share/mysql/russian/errmsg.sys
share/mysql/serbian/errmsg.sys
share/mysql/slovak/errmsg.sys
share/mysql/spanish/errmsg.sys
share/mysql/swedish/errmsg.sys
share/mysql/ukrainian/errmsg.sys
Reference in a new issue Copy permalink