MySQL Connector/C++ 8.0.14 has been released
qlx_store_result() does not return anything through the parameter (which remains unchanged) and finishes with RESULT_ERROR. Enjoy and thanks for the support! On Behalf of Oracle/MySQL Release Engineering Team, Kent Boortz -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Shell 8.0.14 for MySQL Server 8.0 and 5.7 has been released
checking if the Performance Schema was enabled on the target instance. This could result in a situation where you could create a cluster but could not run several management operations on it, for example the Cluster.status() operation. Now, dba.checkInstanceConfiguration() checks that the Performance Schema is enabled on instances. (Bug #25867733) * When JSON format output was enabled for MySQL Shell, the properties of the Shell API Options class (shell.options) and AdminAPI Cluster class (dba.getCluster) were not printed, only the class name. (Bug #25027181) * When Cluster.checkInstanceState() was executed on an instance which was already a member of the current cluster, the output indicated that the instance was fully recoverable. This was misleading and was caused by a missing validation to ensure the instance does not belong to a cluster. (Bug #24942875) * The dba.checkInstanceConfiguration() operation did not recognize privileges when they were associated to a user through a role (available in MySQL server 8.0 and higher). In such a case, a missing privileges error was being incorrectly issued despite the user possessing all the required privileges. Now users with their privileges assigned by roles are recognized by AdminAPI operations correctly. (Bug #91394, Bug #28236922) On Behalf of Oracle/MySQL Release Engineering Team, Kent Boortz -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/ODBC 8.0.13 has been released
Dear MySQL users, MySQL Connector/ODBC 8.0.13 is a new version in the MySQL Connector/ODBC 8.0 series, the ODBC driver for the MySQL Server. The available downloads include both a Unicode driver and an ANSI driver based on the same modern codebase. Please select the driver type you need based on the type of your application - Unicode or ANSI. Server-side prepared statements are enabled by default. It is suitable for use with any MySQL server version from 5.5. This release of the MySQL ODBC driver is conforming to the ODBC 3.8 specification. It contains implementations of key 3.8 features, including self-identification as a ODBC 3.8 driver, streaming of output parameters (supported for binary types only), and support of the SQL_ATTR_RESET_CONNECTION connection attribute (for the Unicode driver only). The release is now available in source and binary form for a number of platforms from our download pages at https://dev.mysql.com/downloads/connector/odbc/ For information on installing, please see the documentation at https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation.html Changes in MySQL Connector/ODBC 8.0.13 (2018-10-22, General Availability) Functionality Added or Changed * Added dynamic libmysql linking support via the -DMYSQLCLIENT_STATIC_LINKING:BOOL=TRUE|FALSE option; defaults to FALSE to enable dynamic linking. Bugs Fixed * Fixed column metadata handling with Microsoft Access. (Bug #28670725, Bug #91856) * The following obsolete options were removed: NO_SCHEMA (use NO_CATALOG instead), DISABLE_SSL_DEFAULT (use SSLMODE instead), and SSL_ENFORCE (use SSLMODE instead). (Bug #28407520) * The ODBC Driver returned 0 for the SQL_MAX_SCHEMA_NAME_LEN attribute, and now returns 64 as the maximum length for a MySQL schema name. (Bug #28385722) * Because the MySQL ODBC driver ignored the SQL_RD_OFF value for the SQL_ATTR_RETRIEVE_DATA attribute, it incorrectly kept writing into the data buffers. This led to write access violation errors when data was written into the buffer when the user application explicitly requested not to write there. (Bug #28098219, Bug #91060) On Behalf of Oracle/MySQL Release Engineering Team, Kent Boortz -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/ODBC 5.3.11 has been released
Dear MySQL users, MySQL Connector/ODBC 5.3.11, a new version of the ODBC driver for the MySQL database management system, has been released. The available downloads include both a Unicode driver and an ANSI driver based on the same modern codebase. Please select the driver type you need based on the type of your application - Unicode or ANSI. Server-side prepared statements are enabled by default. It is suitable for use with any MySQL version from 5.5. This is the fifth release of the MySQL ODBC driver conforming to the ODBC 3.8 specification. It contains implementations of key 3.8 features, including self-identification as a ODBC 3.8 driver, streaming of output parameters (supported for binary types only), and support of the SQL_ATTR_RESET_CONNECTION connection attribute (for the Unicode driver only). The release is now available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/connector/odbc/5.3.html For information on installing, please see the documentation at http://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation.html Changes in MySQL Connector/ODBC 5.3.11 (2018-07-30, General Availability) Functionality Added or Changed * Based on MySQL Client library 5.7.23 it has the support for the new caching_sha2_password authentication method, which allows connecting to MySQL Server 8.0. Bugs Fixed * The Unicode version now uses the UTF8MB4 character set as a transport character set between the MySQL server and the ODBC driver. Because text conversions requested by the ODBC user with the CHARSET connection option are done inside the ODBC Driver after the data is received from the server, it now converts text data as UTF8MB4 to USER_CHARSET instead of UTF8 to USER_CHARSET. (Bug #28204756) * Connections to MySQL Server 8.0 could yield "Source character set not supported by client" errors during sorting and case-sensitive operations. Now known UTF8MB4 collations are used for these operations, such as utf8mb4_general_ci (known to libmysqlclient 5.7) instead of utf8mb4_tolower_ci. (Bug #28116892, Bug #90984) * MySQL Server 8.0 connections could fail with unsupported character sets and collations as utf8mb4_xx collations reported by MySQL Server 8.0 with numbers greater than 250 were unknown to libmysqlclient 5.7. Because collations affect sorting but not the data conversion, they can be substituted with known collations such as utf8mb4_general_ci (45). (Bug #28116892, Bug #90984) * Connector/ODBC is now built with MySQL client library 5.7.23, and commercial builds also use an updated OpenSSL version (v1.0.2o). Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html. (Bug #27829777) * Reported errors that occurred while executing multiple statements with a single query were generic and without context. For example, SQLMoreResults might return "unhandled error from mysql_next_result()" instead of the error reported by MySQL Server. (Bug #11757423, Bug #49466) On Behalf of Oracle/MySQL Release Engineering Team, Kent Boortz -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/ODBC 8.0.11 GA has been released
Dear MySQL users, MySQL Connector/ODBC 8.0.11 is the first GA version of the MySQL Connector/ODBC 8.0 series, the ODBC driver for the MySQL database management system. The available downloads include both a Unicode driver and an ANSI driver based on the same modern codebase. Please select the driver type you need based on the type of your application - Unicode or ANSI. Server-side prepared statements are enabled by default. It is suitable for use with any MySQL server version from 5.5. This release of the MySQL ODBC driver is conforming to the ODBC 3.8 specification. It contains implementations of key 3.8 features, including self-identification as a ODBC 3.8 driver, streaming of output parameters (supported for binary types only), and support of the SQL_ATTR_RESET_CONNECTION connection attribute (for the Unicode driver only). Also, Connector/ODBC 8.0 has a GTK+-based setup library providing a GUI DSN setup dialog on some Unix-based systems, currently included in the Debian 9, EL6/OL6 (64-bit only), EL7/OL7 (64-bit only), Fedora 26/27, FreeBSD 11, SLES 12, and Ubuntu 14/16/17 packages. The release is now available in source and binary form for a number of platforms from our download pages at https://dev.mysql.com/downloads/connector/odbc/ For information on installing, please see the documentation at https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation.html Changes in MySQL Connector/ODBC 8.0.11 (2018-04-19) MySQL Connectors and other MySQL client tools and applications now synchronize the first digit of their version number with the (highest) MySQL server version they support. This change makes it easy and intuitive to decide which client version to use for which server version. Connector/ODBC 8.0.11 is the first release to use the new numbering. It was branched from Connector/ODBC 5.3.10. The Connector/ODBC 8.0 series also adds full MySQL Server 8.0 support. Functionality Added or Changed * Connector/ODBC now supports a new GET_SERVER_PUBLIC_KEY connection option that enables requesting the RSA public key from the server. For accounts that use the caching_sha2_password or sha256_password authentication plugin, this key can be used during the connection process for RSA key-pair based password exchange with TLS disabled. This capability requires a MySQL 8.0 or higher server, and is supported only for Connector/ODBC built using OpenSSL. * A new OpenSSL runtime dependency was added that must be present on the target system where the connector is used. For some platforms it is assumed that a system-wide OpenSSL is available, for others, such as Windows and macOS, these required OpenSSL libraries are bundled in the binary packages. * Packaging was modified for the new MySQL Connector/ODBC 8 series. For example, the Connector/ODBC 5.x ODBC driver has a file named myodbc5w.dll, whereas this same ODBC 8.0 driver is named myodbc8w.dll for the Connector/ODBC 8.x series. The sample .ini file also references these new file names. On Behalf of Oracle/MySQL Release Engineering Team, Kent Boortz -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Shell 8.0.3-dmr has been released
ll could hang when Ctrl + C was used to exit the
shell. (Bug #25180850, Bug #84022)
* Attempting to create a multi-primary cluster in
interactive mode failed unless you passed in the {force:
true} option. Now when you confirm that you understand
the impact of using multi-primary mode the command
correctly creates a multi-primary cluster.
(Bug #25034951)
* The removeInstance() was not working on stopped instances
and it was not possible to remove an unavailable instance
from the cluster. The fix adds a new option force to the
removeInstance() command to enable you to remove
instances from the metadata that are permanently not
available, avoiding obsolete data from being kept in the
metadata of the cluster. In addition the error message
provided when not using the force option has been
improved and the online help for the removeInstance() was
also updated accordingly. (Bug #24916064)
* Unsigned data could be incorrectly read from the
database. (Bug #24912358)
* The parsing of Unix sockets provided as part of a URI has
been improved. (Bug #24905066)
* The error messages generated by issuing
dba.deployLocalInstance() against an unsuitable or
incompatible instance have been improved. (Bug #24598272)
* The dba.createCluster(), dba.getCluster(), and
dba.rebootClusterFromCompleteOutage() functions have been
updated to validate the cluster name, using the following
rules:
+ Name must start with a letter or the '_' character
+ Name can only contain alphanumeric characters and
the '_' character
+ Cannot be longer than 40 characters
+ Cannot be empty
The Cluster.addInstance() function has been updated to
validate the label used on an instance in the cluster,
using the following rules:
+ Label can only contain alphanumerics or the '_'
character
+ Cannot be longer than 256 characters
+ Cannot be empty
(Bug #24565242)
* MySQL Shell now accepts Unicode characters as input.
(Bug #23151666, Bug #81176)
On Behalf of the MySQL/ORACLE RE Team
Kent Boortz
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/C++ 8.0.5-dmr has been released
lx_session_t *sess = mysqlx_get_session_from_options(
sess_opt, err_buf, &err_code
);
* The NodeSession class has been renamed to Session, and
the XSession class has been removed.
* Connections created using Session objects now are secure
by default. Also, the ssl-enabled connection option has
been replaced by ssl-mode. Permitted ssl-mode values are
disabled, required (the default), verify_ca and
verify_identity.
* Option names within connection strings are now treated as
case insensitive. Option values are still case sensitive
by default.
Bugs Fixed
* It is now possible to call stmt.execute() multiple times.
Calling methods that modify statement parameters should
modify the statement sent with execute(). This is also
true for binding new values to named parameters.
(Bug #25858159)
* Compiler errors occurred when creating a SessionSettings
object due to ambiguity in constructor resolution.
(Bug #25603191)
* collection.add() failed to compile if called with two STL
container arguments. (Bug #25510080)
* These expression syntaxes are now supported:
CHARSET(CHAR(X'65'))
'abc' NOT LIKE 'ABC1'
'a' RLIKE '^[a-d]'
'a' REGEXP '^[a-d]'
POSITION('bar' IN 'foobarbar')
These expression syntaxes are not supported but a better
error message is provided when they are used:
CHARSET(CHAR(X'65' USING utf8))
TRIM(BOTH 'x' FROM 'xxxbarxxx')
TRIM(LEADING 'x' FROM 'xxxbarxxx')
TRIM(TRAILING 'xyz' FROM 'barxxyz')
'Heoko' SOUNDS LIKE 'h1aso'
(Bug #25505482)
On Behalf of the MySQL/Oracle Release Engineering Team,
Kent Boortz
--
Kent Boortz, Release Staff engineer
Oracle, The MySQL Team
Mobile: +46 76 77 69 049
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
MySQL Shell 1.0.8 RC has been released
ted to include all of the available global objects. (Bug #24764191) * When using the shell.prompt() function, providing an invalid type was not generating the appropriate error. (Bug #24763825) * The way MySQL Shell processes commands has been improved to properly handle spaces in the command line, and support was added for quoted parameters when spaces are used. To pass a parameter with spaces surround it with double quotes, and if double quotes are part of the parameter they can be escaped using \". (Bug #24762017) * Primitive numeric types and booleans were not being automatically converted between each other following the Python type conversion rules. The fix ensures that a statement such as dba.verbose=1 is valid, in other words when a == b is true, then b is assignable to a as is typical in Python. (Bug #24744707) * Using --log-level=5 or greater wrote passwords to the log as plain text. (Bug #24735878) * The --log-level command option can now use named log levels such as debug3. (Bug #24735532) * When an SQL statement followed the terminating character of an SQL comment that ended with */ it could result in unexpected behavior because the first character of the statement following the comment was being ignored. The fix ensures inline comments in SQL statements are correctly parsed. (Bug #24671436) * Results output when using the --json option now go inside of a JSON object. (Bug #24575611) * When using the help, space characters at the end of a line were causing the requested help topic to not be found. (Bug #24522689) * When using SQL mode the usage of single quotes in escaping has been made consistent with the handing in MySQL, for example SELECT '''' as a;. (Bug #24380669, Bug #82381) * The help for XSession was suggesting SQL mode was available which was incorrect. (Bug #23065163) * When using SQL mode the command history was removing the semicolon from the end of previously issued lines (Bug #21390737) On behalf of the MySQL Release Team Kent Boortz -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.2.19 has been released
tive. This was because MySQL Cluster allowed an Ndb_cluster_connection object be to deleted while some Ndb instances were still active, which might result in the usage of null pointers by ClusterJ. This fix stops that happening by preventing ClusterJ from closing a session factory when any of its sessions are still active. (Bug #19846392) References: See also Bug #1242. On behalf of the Oracle/MySQL RE Team, Kent Boortz -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/ODBC 5.3.0 alpha has been released
Dear MySQL users, MySQL Connector/ODBC 5.3.0 alpha, a new version of the ODBC driver for the MySQL database management system, has been released. The available downloads include both a Unicode driver and an ANSI driver within the same package. Server-side prepared statements are enabled by default. It is suitable for use with any MySQL version since 4.1 (It will not work with 4.0 or earlier releases.) This is first MySQL ODBC driver conforming to the ODBC 3.8 specification. We did the minimally required implementation of the standard with key 3.8 feature, in this release being output stream parameters supported for binary types only. Also Connector/ODBC 5.3 introduces a GTK+-based setup library providing GUI DSN setup dialog on some Unix based systems, currently included in the Oracle Linux 6 and Debian 6 binary packages. Other new features in the 5.3 driver are FileDSN and Bookmarks support. Keep in mind that this is a alpha release, and as with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. Not all of the features planned for the final Connector/ODBC 5.3 release are implemented. The release is now available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/connector/odbc/5.3.html For information on installing, please see the documentation at http://dev.mysql.com/doc/refman/5.6/en/connector-odbc-installation.html Enjoy! The MySQL Connectors team at Oracle == Functionality added or changed, and bugs fixed: * Support for File Data Sources. (WL#6583, Bug# 11746219/24581) * Bookmark support added in myodbc (WL#7039) * Added new variable in cmake config files ODBCCP32_LIB for odbccpp32.lib path, and MYSQLCLIENT_LIB_NAME for linking mysqlclient statically or dynamically by specifying mysqlclient library (libmysql.*, mysqlclient.*, libmysqlclient_r.*, libmysqlclient.*) to be used. Mysql CPP linkage for mysql version >= 5.6.4 (wl#6738) * Added a new test module for crash bugs (my_crash.c) * Added GUI dialog for Linux * Support of ODBC 3.8 standard - driver self identification, input/output stream parameters (WL#6584) Bugs fixed: * With utf8 byte string for mysql server version < 5.5.3, insert fails with error message "Server does not support 4-byte encoded UTF8 characters." (Bug# 14838690) * Driver use the char ';' as separator in attributes string instead of the '\0' (Bug# 15940689/66548) * DSN connection parameters override those specified in the connection string (Bug# 11760574/52996) * Non-compliant behavior of SQLMoreResults (Bug# 16101282/67920) * MSSQL linked server connected to MySQL 5.1.9 driver causes hard crash (Bug# 16604346/63386) * MySQL ODBC drivers incorrectly returns TIME columns, where value > '99:59:59' (Bug# 16176981/67793) * Conversion of Time field data to Timestamp type may produce incorrect result (Bug# 17016839/69545) * Need to add a lock to access connections member in ENV structure (Bug# 17240611/69864) * Visual Studio 2010 crashes when reading rows from any table in Server Explorer (Bug# 17304031/69950) * Corrected MYSQL_NUM_VERSION calculation error in FindMysql.cmake. MYSQL_LIB_DIR, MYSQL_INCLUDE_DIR, MYSQL_LINK_FLAGS and MYSQL_CXXFLAGS will be obtained from mysql_config only when they are not provided using cmake options. * Memory leak in SQLPrepare with queries that use parameters (Bug# 17400483/70113) * Valgrind error, simple loop fix (Bug# 17397596/64105) * Wrong pointer type can cause crash in convert_c_type2str() (Bug# 17421620/69733) * Memory leak in SQLMoreResults() as deallocation of result_bind buffer required before calling mysql_stmt_free_result() (Bug# 17441296) * FileDSN is created even if the connection credentials are wrong (Bug# 17508006) * Error with iodbc in SQLAllocHandle with handle type SQL_HANDLE_DBC as odbc_ver is unset. Built against the MySQL server 5.6.14 client library. -- Kent Boortz, Release Staff engineer Oracle, The MySQL Team -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/ODBC 5.2.6 has been released
Dear MySQL users,
MySQL Connector/ODBC 5.2.6, a new version of the ODBC driver for the
MySQL database management system, has been released.
The available downloads include both a Unicode driver and an ANSI
driver based on the same modern codebase. Please select driver type
you need based on the type of your application - Unicode or ANSI.
Server-side prepared statements are enabled by default. It is suitable
for use with any MySQL version since 4.1 (It will not work with 4.0 or
earlier releases.)
The release is now available in source and binary form for a number of
platforms from our download pages at
http://dev.mysql.com/downloads/connector/odbc/5.2.html
MySQL Connector/ODBC 5.2.6 will also be available for downloads via the
Oracle Software Delivery Cloud in approximately 1-2 weeks.
For information on installing, please see the documentation at
http://dev.mysql.com/doc/refman/5.6/en/connector-odbc-installation.html
Enjoy!
The MySQL Connectors team at Oracle
==
Changes in MySQL Connector/ODBC 5.2.6
Functionality Added or Changed
* Added a lock in the ENV structure against simultaneous accesses to
an environment handle's connection list, in order to avoid memory
access issues that might occur when multiple threads share the same
environment handle. (Bug #17240611, Bug #69864)
Bugs Fixed
* Memory leaks occurred in SQLPrepare() and SQLExecDirect() when
SQLBindParamater was used on the SQL statements. This fix frees
previous results of mysql_stmt_result_metadata() in order to prevent
the memory leaks. (Bug #17400483, Bug #70113)
* The exit condition for a for loop in stringutil.c is changed to
avoid a possible out-of-bounds error and the associated reports by
Valgrind. (Bug #17397596, Bug #64105)
* Microsoft Visual Studio 2010 crashed when reading rows from any
table in Server Explorer with connections to DSNs made by
Connector/ODBC. (Bug #17304031, Bug #69950)
* When SQL TIME data was converted to the C data type of TIMESTAMP, if
the value of the hour field is greater than 24, the date fields did
not get set to the current date and the fraction field for seconds
did not get set to zero as required by the ODBC specifications.
(Bug #17016839, Bug #69545)
* When trying to create a linked server in Micrsoft SQL Server 2008 to
a MySQL server set up with Connector/ODBC as a DSN, the Microsoft
SQL Server (if it is a 64-bit version) crashed or the linked server
suffered a catastrophic failure (if a 32-bit version of the
Microsoft SQL Server is used). (Bug #16604346, Bug #63386)
* When reading TIME column data using the SQLGetData method into the
SQL_C_TYPE_TIME datatype, errors occured when the time string
contained more than 6-digits (e.g., 120:53:44).
(Bug #16176981, Bug #67793)
* When called after SQLPrepare, the funciton SQLMoreResults returned
SQL_ERROR, instead of SQL_NO_DATA as required by the ODBC
specification. (Bug #16101282, Bug #67920)
* Connector/ODBC used the ";" character instead of a null byte ("\0")
to terminate keyword-value pairs in attribute strings.
(Bug #15940689, Bug #66548)
* When using the Unicode-enabled version of the Connector/ODBC driver
to connect to any MySQL server of version 5.5.2 or older, all
statements failed with the error message .Server does not support
4-byte encoded UTF8 characters.. (Bug #14838690, Bug #67428)
* The configured values of a DSN's parameters overrode the values
provided through the connection string, instead of the other way
round. (Bug #11760574, Bug #52996)
Built against the MySQL server 5.6.14 client library.
--
Kent Boortz, Release Staff engineer
Oracle, The MySQL Team
Mobile: +46 76 77 69 049
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/C 6.1.2 has been released
Dear MySQL users, MySQL Connector/C 6.1.2, a new version of the C API for client/server communication for the MySQL database management system, has been released. This version of Connector/C provides full support for MySQL 5.6 protocol. Connector/C is compatible with the client libraries (libmysql). It includes all the features in the MySQL client library shipped with MySQL servers 5.6 as well as prior versions. You can recompile existing code linked with Connector/C 6.1.2 without any code changes. You can use Connector/C to run and build client applications which communicate with MySQL server versions from 4.1 to 5.6 without a need to do a complete server installation. The release is now available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/connector/c/ MySQL Connector/C 6.1.2 will also be available for downloads via the Oracle Software Delivery Cloud in approximately 1-2 weeks. For information on installing, please see the documentation at http://dev.mysql.com/doc/connector-c/en/connector-c-installation.html Enjoy! Kent Boortz The MySQL build team at Oracle == Functionality Added or Changed * The implementation of condition variables specific to Windows XP and Windows Server 2003 was removed from the source code because MySQL is not supported on those platforms as of MySQL 5.6. Note This change has the following implication: Previously, Connector/C 6.1, while not officially supported on Windows XP or Windows Server 2003, could be used on those platforms. This is no longer possible. (Bug #17332056) * MySQL now supports the use of client-side plugins that implement tracing of communication between a client and the server that takes place using the client/server protocol. Protocol trace plugins use the client plugin API (see Writing Plugins (http://dev.mysql.com/doc/refman/5.6/en/writing-plugins.html)) In Connector/C source distributions, a test protocol trace plugin is implemented in the test_trace_plugin.cc file in the libmysql directory. This can be examined as a guide to writing other protocol trace plugins. * Static libraries built with VS2008, VS2010, VS2012 are now distributed as part of Connector/C packages for Windows: ZIP and MSI. New directories named vs9, vs10, and vs11 located under the lib directory contain static libraries and corresponding pdb files built with VS2008, VS2010, and VS2012, respectively. Bugs Fixed * The CLIENT_CONNECT_WITH_DB flag was improperly handled in the C client library. This could lead to a malformed packet sent to the server. (Bug #17351732) * The mysql_real_connect() C API function could leak memory if it failed. (Bug #17337684) * The mysql_options() C API function could leak memory if called more than once with the MYSQL_SET_CLIENT_IP option. (Bug #17297012) * The Connector/C MSI package was missing the following files: ChangeLog, README, LICENSE, COPYING, INFO_SRC, INFO_BIN. (Bug #17261526) * The Connector/C RPM package was missing the following files: INFO_SRC, INFO_BIN, my_print_defaults, perror. (Bug #17261610) * On Windows, a MySQL client program that simply used #include could not be compiled due to missing Windows declarations in that file. The same program would compile on other platforms. (Bug #16409270) * The libmysql.dll library was missing several symbols: my_init, mysql_client_find_plugin, mysql_client_register_plugin, mysql_load_plugin, mysql_load_plugin_v, and mysql_plugin_options. (Bug #69204, Bug #16797982) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/C 6.1.0 has been released
Dear MySQL users, MySQL Connector/C 6.1.0, a new version of the C API for client/server communication for the MySQL database management system, has been released. This version of Connector/C has the same feature set as the client library shipped with latest MySQL server 5.6 and supports all client/server protocol features present in the server. You can use Connector/C to run and build client applications which communicate with MySQL server versions from 4.1 to 5.6 without a need to do a complete server installation. The release is now available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/connector/c/ For information on installing, please see the documentation at http://dev.mysql.com/doc/connector-c/en/connector-c-installation.html Enjoy! The MySQL build team at Oracle == MySQL Connector/C 6.1 provides these features not present in 6.0: * Support for the pluggable authentication framework that enables implementation of authentication methods as plugins. This framework can be used for MySQL native authentication as well as external authentication methods. See Pluggable Authentication (http://dev.mysql.com/doc/refman/5.6/en/pluggable-authentication.html). * Client-side support for the SHA-256, PAM, and Windows native authentication plugins. See The SHA-256 Authentication Plugin (http://dev.mysql.com/doc/refman/5.6/en/sha256-authentication-plugin.html), The PAM Authentication Plugin (http://dev.mysql.com/doc/refman/5.6/en/pam-authentication-plugin.html), The Windows Native Authentication Plugin (http://dev.mysql.com/doc/refman/5.6/en/windows-authentication-plugin.html). The older MySQL Connector/C 6.0 can connect only to accounts that use native MySQL passwords. If a client program attempts to connect to an account that requires a different authentication method, an "Access denied for user" error occurs. * Support for connecting to accounts that have expired passwords. See Password Expiration and Sandbox Mode (http://dev.mysql.com/doc/refman/5.6/en/password-expiration.html). * Support for prepared CALL (http://dev.mysql.com/doc/refman/5.6/en/call.html) statements. This enables client programs to handle stored procedures that produce multiple result sets and to obtain the final value of OUT and INOUT procedure parameters. See C API Support for Prepared CALL Statements (http://dev.mysql.com/doc/refman/5.6/en/c-api-prepared-call-statements.html). * Support for connecting over IPv6. See IPv6 Support (http://dev.mysql.com/doc/refman/5.6/en/ipv6-support.html). * Support for binding client programs to a specific IP address at connect time. See mysql_options() (http://dev.mysql.com/doc/refman/5.6/en/mysql-options.html). * Support for specifying connection attributes to pass to the server at connect time. See mysql_options() (http://dev.mysql.com/doc/refman/5.6/en/mysql-options.html), and mysql_options4() (http://dev.mysql.com/doc/refman/5.6/en/mysql-options4.html). -- Kent Boortz, Release Staff engineer Oracle, The MySQL Team Mobile: +46 76 77 69 049 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/ODBC 5.2.4 has been released
Dear MySQL users, MySQL Connector/ODBC 5.2.4, a new version of the ODBC driver for the MySQL database management system, has been released. The available downloads include both a Unicode driver and an ANSI driver based on the same modern codebase. Please select driver type you need based on the type of your application - Unicode or ANSI. Server-side prepared statements are enabled by default. It is suitable for use with any MySQL version since 4.1 (It will not work with 4.0 or earlier releases.) The release is now available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/connector/odbc/5.2.html For information on installing, please see the documentation at http://dev.mysql.com/doc/refman/5.5/en/connector-odbc-installation.html Enjoy! The MySQL build team at Oracle == Changes in MySQL Connector/ODBC 5.2.4 (5 February, 2013) This release fixes any bugs encountered since Connector/ODBC 5.2.3. Its main focus is on compatibility with the latest features of MySQL 5.6. Functionality Added or Changed * The new connection option can_handle_exp_pwd indicates that your application includes error-handling logic to deal with the error code for an expired password. See Connector/ODBC Connection Parameters (http://dev.mysql.com/doc/refman/5.5/en/connector-odbc-configu ration-connection-parameters.html) for the details of this connection option and the associated SQL state and native error code. See ALTER USER Syntax (http://dev.mysql.com/doc/refman/5.6/en/alter-user.html) for details about password expiration for MySQL server accounts. This new option is added to the Windows GUI, through a checkbox Can Handle Expired Password on the Connection tab of the Details dialog. * The following reserved words were added to the list returned by the SQLGetInfo() ODBC function, for compatibility with the latest MySQL 5.6 syntax: + GET + IO_AFTER_GTIDS + IO_BEFORE_GTIDS + MASTER_BIND + ONE_SHOT + PARTITION + SQL_AFTER_GTIDS + SQL_BEFORE_GTIDS Bugs Fixed * When a column with type TINYTEXT, TEXT, MEDIUMTEXT, or LONGTEXT was retrieved from a table with a binary collation, the text fields were converted to a hexadecimal representation, even though these values were not really BLOBs. The unnecessary conversion could expand the data, causing overflow problems when storing the result values. (Bug #11746572, Bug #27282) Thanks, RE Team. -- Kent Boortz, Release Staff engineer Oracle, The MySQL Team Mobile: +46 76 77 69 049 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/C++ 1.1.2 has been released
Dear MySQL Users, A new GA (general availability) version of MySQL Connector/C++ has been made available: MySQL Connector/C++ 1.1.2 GA. The MySQL Connector/C++ provides a C++ API for connecting client applications to the MySQL Server 5.1 or newer. You can download the production release at: http://dev.mysql.com/downloads/connector/cpp/1.1.html The MySQL driver for C++ offers an easy to use API derived from JDBC 4.0. MySQL Workbench is using it successfully since years. We have improved the driver since the last GA release. Please see the documentation and the CHANGES file in the source distribution for a detailed description of bugs that have been fixed. Bug descriptions are also listed below. Enjoy! The MySQL build team at Oracle == Changes in MySQL Connector/CPP 1.1.2 (5 February, 2013) Bugs Fixed * Connector/C++ applications could not handle connecting to the server using an account for which the password had expired. Connector/C++ now supports three new connection options: + OPT_CAN_HANDLE_EXPIRED_PASSWORDS: If true, this indicates to the driver that the application can handle expired passwords. If the application specifies OPT_CAN_HANDLE_EXPIRED_PASSWORDS but the underlying libmysql library does not support it, the driver returns sql::mysql:deCLIENT_DOESNT_SUPPORT_FEATURE(820). + preInit: A string containing queries to run before driver initialization. + postInit: A string containing queries to run after driver initialization. A new file driver/mysql_error.h is being added to the MSI package. This file defines an enum DRIVER_ERROR, which contains the definition of deCL_CANT_HANDLE_EXP_PWD. In addition to the preceding changes, these problems with Statement::executeUpdate were fixed: + If Statement::executeUpdate executed multiple statements, the connection became unusable. + There was no exception if one of queries returned a resultset. Now executeUpdate returns and update count for the last executed query. For example code showing how to use the new options, see the file test/unit/bugs/bugs.cpp in the Connector/C++ distribution. (Bug #67325, Bug #15936764) Thanks, RE Team -- Kent Boortz, Release Staff engineer Oracle, The MySQL Team Mobile: +46 76 77 69 049 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/ODBC 5.1.12 has been released
s, RE Team -- Kent Boortz, Release Staff engineer Oracle, The MySQL Team Mobile: +46 76 77 69 049 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/ODBC 5.2.3 has been released
Dear MySQL users, MySQL Connector/ODBC 5.2.3, a new version of the ODBC driver for the MySQL database management system, has been released. The available downloads include both a Unicode driver and an ANSI driver based on the same modern codebase. Please select driver type you need based on the type of your application - Unicode or ANSI. Server-side prepared statements are enabled by default. It is suitable for use with any MySQL version since 4.1 (It will not work with 4.0 or earlier releases.) The release is now available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/connector/odbc/5.2.html For information on installing, please see the documentation at http://dev.mysql.com/doc/refman/5.5/en/connector-odbc-installation.html We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: https://wikis.oracle.com/display/mysql/Contributing Enjoy! The MySQL build team at Oracle == Bugs Fixed * Insert operations could fail if the inserted values contained any bit fields, mapped to table columns declared as bit(1): Data too long for column 'column_name' (Bug #15997361, Bug #67702) * The is_minimum_version function could return an incorrect result in some cases where the difference was in the third component of the release number. (Bug #15926340) * An application making extensive use of prepared statements could encounter an error: Can't create more than max_prepared_stmt_count statements (current value: 16382) The issue occurred even if SQLFreeStmt() calls were used. The Prepared_stmt_count value grew until it exceeded the internal limit. A workaround was to disable server-side prepared statements. (Bug #14812778, Bug #67340) * On a 64-bit system, calls to the SQLBindCol function using indicator variables (through the last parameter) could return incorrect results. (Bug #11766437, Bug #59541) Built against the MySQL server 5.5.27 client library. -- Kent Boortz, Release Staff engineer Oracle, The MySQL Team Mobile: +46 76 77 69 049 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/Python 1.0.7 has been released
Dear MySQL users, MySQL Connector/Python v1.0.7 is a new version of the pure Python database driver for MySQL. This is the first GA (General Availability) version of Connector/Python v1.0. MySQL Connector/Python version 1.0 is compatible with MySQL Server versions 5.5 and greater, but should work with earlier versions (greater than v4.1). Python v2.6 and greater as well as Python v3.1 and greater are supported. Python v2.4 and v2.5 are known to work, but are not officially supported. MySQL Connector/Python v1.0.7 is available for download from http://dev.mysql.com/downloads/connector/python/#downloads A brief summary of changes in MySQL Connector/Python v1.0 is listed below. Please check the ChangeLog file inside the distribution for a more complete list of changes. Changes in MySQL Connector/Python v1.0.7 Bug Fixes: * Fixed formatting of client errors changing numeric to string placeholders. (Bug #14548043) Additionally, the client and server errors have been regenerated using latest development release of MySQL v5.6. Documentation - Online: http://dev.mysql.com/doc/connector-python/en/index.html The source distribution includes the manual in various formats under the docs/ folder. Reporting Bugs -- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy! The MySQL build team at Oracle -- Kent Boortz, Release Staff engineer Oracle, The MySQL Team Mobile: +46 76 77 69 049 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/ODBC 5.2.2 has been released
Dear MySQL users, MySQL Connector/ODBC 5.2.2, a new version of the ODBC driver for the MySQL database management system, has been released. This is the first GA release for the Connector/ODBC 5.2.x series. Now the available downloads include both a Unicode driver and an ANSI driver based on the same modern codebase. Please select driver type you need based on the type of your application - Unicode or ANSI. Server-side prepared statements are enabled by default. It is suitable for use with any MySQL version since 4.1 (It will not work with 4.0 or earlier releases.) The release is now available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/connector/odbc/5.2.html For information on installing, please see the documentation at http://dev.mysql.com/doc/refman/5.5/en/connector-odbc-installation.html We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: https://wikis.oracle.com/display/mysql/Contributing Enjoy! The MySQL build team at Oracle == Functionality Added or Changed * The implementation of the SQLBindParameter() function was enhanced to support "out" and "inout" parameters when calling stored procedures. Designate the bind parameters intended to hold output values from stored procedures using the type specifiers SQL_PARAM_OUTPUT or SQL_PARAM_INPUT_OUTPUT. Note Currently, the support for "out" and "inout" parameters does not apply to LONGTEXT and LONGBLOB columns in ADO. * Server-side prepared statements are now enabled by default. To revert to the former behavior, using client-side emulation for prepared statemnts, specify the NO_SSPS option when configuring the DSN. * The download page now offers choices of a Unicode driver or an ANSI driver. Now users can get an ANSI driver with the combination of high performance and the latest standard-compliant behavior, rather than staying on the older 3.51 codebase. Bugs fixed: * Server disconnects on the execution of a query following execution of a SP returning resultset(s) and OUT parameters. (Bug# 14512187) * Crash while executing after binding BLOB datatype as INOUT parameter (Bug# 14501952) * SP having 2 BLOB OUT parameters crashes at execution (Bug# 14563386) * ASSERT for INOUT parameter of BIT(N>3) type (Bug#14560916) * Using ADO, driver returns wrong type and value for bit(>1) parameter (Bug# 14555713) * Blobs used in as INOUT parameters have inconsistent behaviour in ADO (Bug# 14580316) * my_isspace calls cause ODBC driver crashes (Bug# 14363601) * SQLNativeSql did not null-terminate output string after copying (Bug# 14559721) * Incorrect length value passed to SQLSetConnectAttr could cause driver crash. (Bug# 14620420) Built against the MySQL server 5.5.27 client library. -- Kent Boortz, Release Staff engineer Oracle, The MySQL Team Mobile: +46 76 77 69 049 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/Python 1.0.6 beta has been released
Dear MySQL users, MySQL Connector/Python v1.0.6 is a new version of the pure Python database driver for MySQL. This is the first in a series of beta releases that will introduce users to new features and changes. This release is feature complete, but as a non-GA release is not recommended for use in production environments. MySQL Connector/Python version 1.0 is compatible with MySQL Server versions 5.5 and greater, but should work with earlier versions (greater than v4.1). MySQL Connector/Python v1.0.6 (beta) is available for download from http://dev.mysql.com/downloads/connector/python/#downloads (Note: not all mirrors may be up to date yet) A brief summary of changes in MySQL Connector/Python v1.0 is listed below. Please check the ChangeLog file inside the distribution for a more complete list of changes. Changes in MySQL Connector/Python v1.0.6 Functionality Added or Changed: * Changed name and version of distributions to align with other MySQL projects. The version now includes the suffix 'b' for beta and 'a' for alpha followed by a number. This version is used in the source and built distributions. GA versions will have no suffix. The RPM spec files have been updated to create packages whose names are aligned with RPMs from other MySQL projects. * Changed how MySQL server errors are mapped to Python exceptions. We now use the SQLState (when available) to raise a better error. Incompatibility: some server errors are now raised with a different exception. * It is possible to override how errors are raised using the mysql.connector.custom_error_exception() function, defined in the mysql.connector.errors module. This can be useful for certain frameworks to align with other database drivers. Bug Fixes: * Fixed version-specific code so Connector/Python works with Python 3.3. (Bug #14524942) * Fixed MySQLCursorRaw.fetchall() so it does not raise an exception when results are available. (Bug #14517262, Bug #66465) * Fixed installation of version.py on OS X: version.py is now correctly installed on OS X in the mysql.connector package. Previously, it was installed through data_files, and version.py ended up in the system-wide package location of Python, from which it could not be imported. data_files is not used any longer in setup.py and is removed. Extra files like version.py are now copied in the custom Distutils commands. (Bug #14483142) * Timeout for unit tests has been set to 10 seconds. Test cases can individually adjust it to be higher or lower. (Bug #14487502) * Fixed test cases in test_mysql_database.py that failed when using YEAR(2) with MySQL 5.6.6 and greater. (Bug #14460680) * Fixed SSL unit testing for source distributions: The SSL keys and certificates were missing and are now added to the source distribution. Now SSL testing works properly. Additionally for the Windows platform, forward slashes were added to the option file creation so the MySQL server can pick up the needed SSL files. (Bug #14402737) Documentation - Online: http://dev.mysql.com/doc/connector-python/en/index.html The source distribution includes the manual in various formats under the docs/ folder. Reporting Bugs -- We welcome and appreciate your feedback and Bug reports: http://bugs.mysql.com/ Enjoy! On behalf of the MySQL Build Team, Kent Boortz -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/ODBC 5.2.1 beta has been released
Dear MySQL users, MySQL Connector/ODBC 5.2.1 beta, a new version of the ODBC driver for the MySQL database management system, is available for download. The 5.2 driver series is suitable for use with any MySQL server version since 4.1. (It will not work with 4.0 or earlier releases.) This new version of MySQL Connector/ODBC combines both existing driver series, the ANSI driver is an upgrade to the 3.51 series, and the Unicode driver is an upgrade to the 5.1 series. The beta release is available now, in source and binary form for a number of platforms, from our download pages at http://dev.mysql.com/downloads/connector/odbc/5.2.html and mirror sites. Note that not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. For information on installing, please see the documentation at http://dev.mysql.com/doc/refman/5.5/en/connector-odbc-installation.html We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: https://wikis.oracle.com/display/mysql/Contributing Enjoy! The MySQL Connectors team at Oracle == Functionality added or changed: * Driver prepares statements on server * Support of INOUT and OUT parameters(WL#6116) Bugs fixed: * Long table names crash OBDC driver. (Bug# 14085211/65200) * Close proximity issue when handling OS signlals in myodbc (Bug# 14303803) * "String data right truncated" error is not always correct (Bug# 14285620) Built against the MySQL server 5.5.27 client library. -- Kent Boortz, Release Staff engineer Oracle, The MySQL Team Mobile: +46 76 77 69 049 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/C++ 1.1.1 has been released
Dear MySQL Users, A new GA (general availability) version of MySQL Connector/C++ has been made available: MySQL Connector/C++ 1.1.1 GA. The MySQL Connector/C++ provides a C++ API for connecting client applications to the MySQL Server 5.1 or newer. You can download the production release at: http://dev.mysql.com/downloads/connector/cpp/1.1.html The MySQL driver for C++ offers an easy to use API derived from JDBC 4.0. MySQL Workbench is using it successfully since years. We have improved the driver since the last GA release. Please see the documentation and the CHANGES file in the source distribution for a detailed description of bugs that have been fixed. The following features and bug fixes have been added: * DatabaseMetaData::getSQLKeywords() updated to match MySQL 5.5. Note that C/C++, just like C/JDBC, returns the same list for every MySQL database version. * Added MySQL_Connection::getLastStatementInfo() which returns back the value of the mysql_info() function of the MySQL Client Library (libmysql). * Added new method ResultSetMetaData::isNumeric() and implemented it in all classes that subclass from it. * Fixed the bug causing compilation errors in Microsoft Visual Studio 2010 if stdint.h was included. See http://bugs.mysql.com/bug.php?id=60307 * Fixed bug making statement that did not raise any warning to return warnings from previously executed statement. * Fixed stores(Lower|Mixed)Case(Quoted)Identifiers methods. * URI format has been extended to better fit IPv6 addresses. You now can use [] to separate host part of the URI. * Built against libmysql 5.5.27 enabling support of authentification plugins and IPv6. You can find further details, including usages examples, in the documentation at: http://dev.mysql.com/doc/en/connector-cpp.html You may also want to contribute to the MySQL Forum on C/C++ at http://forums.mysql.com/list.php?167 or join the MySQL Connector/C++ mailing list http://lists.mysql.com/connector-cplusplus . We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy! On behalf of the MySQL Build Team, Kent Boortz -- Kent Boortz, Release Staff engineer Oracle, The MySQL Team Mobile: +46 76 77 69 049 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/Python 1.0.5 beta has been released
Dear MySQL users, MySQL Connector/Python v1.0.5 is a new version of the pure Python database driver for MySQL. This is the first in a series of beta releases that will introduce users to new features and changes. This release is feature complete, but as a non-GA release is not recommended for use in production environments. MySQL Connector/Python version 1.0 is compatible with MySQL Server versions 5.5 and greater, but should work with earlier versions (greater than v4.1). MySQL Connector/Python v1.0.5 (beta) is available for download from http://dev.mysql.com/downloads/connector/python/#downloads (Note: not all mirrors may be up to date yet) A brief summary of changes in MySQL Connector/Python v1.0 is listed below. Please check the ChangeLog file inside the distribution for a more complete list of changes. Changes in MySQL Connector/Python v1.0.5 This section documents changes and Bug fixes that have been applied in MySQL Connector/Python since the development release v0.3.2. Functionality Added or Changed: * Adding support for time values with a fractional seconds part. A new example script microseconds.py was added to show this functionality. * Refactored the modules connection and protocol and created a new module network. The MySQLProtocol does not keep a reference to the connection object any more and deals only with creating and parsing MySQL packets. Network interaction is now done by the MySQLConnection objects (with the exception of MySQLProtocol.read_text_result()). * Added MySQLConnection.reconnect() which used to reconnect to the MySQL server. It accepts number of retries and a delay between attempts. * Added descriptive error codes for both client and server errors in the module errorcode. A new sub-package locales has been added, which currently only support English client error messages. * Added SQLMode class in the constants module, making it easier to use them. * Incompatible Change: The MySQLConnection.ping() method raises an InterfaceError when the MySQL server is not available. It can also optinally reconnect and accepts the same arguments as the reconnect() method. * Incompatible Change: The MySQLConnection.is_connect() method now returns True or False. It can be used to simply check whether a connection is available or not. * Incompatible Change: MySQLCursor.execute() does not return anything for single statement operations. Sending multiple statements will result in a generator object to be returned by MySQLCursor.execute(). The MySQLCursor.next_resultset() became obsolete and was removed and the MySQLCursor.next_proc_result() method has been renamed to MySQLCursor.proc_results(), which returns a generator object. The MySQLCursor.with_rows property can be used to check if a result could return rows. The multiple_resultset.py example script shows how to go through results produced by sending multiple statements. (Bug #14208326) * Incompatible Change: The method MySQLConnection.set_charset() has been removed and replaced by MySQLConnection.set_charset_collation() to simplify setting and retrieving character set and collation information. The MySQLConnection properties collation and charset are now read-only. (Bug #14260052) * Incompatible Change: The MySQLConnection methods unset_client_flag() and set_client_flag() have been removed. Use the set_client_flags() method instead using a sequence. (Bug #14259996) Bug Fixes: * Fixed MySQLCursor.executemany() when INSERT statements use the 'ON DUPLICATE KEY'-clause with a function like VALUES(). (Bug #14259954, Bug #65678) * Fixed cursor.CursorBase attributes description, lastrowid and rowcount to be read-only properties. (Bug #14231160) * Fixed and refactored mysql.connector.errors module. (Bug #14039339) * Fixed MySQLCursor.description so column names are Unicode. (Bug #13792575) * Fixed automatic garbage collection which caused memory usage to grow over time. (Bug #13435186) * Fixed setting time zone for current MySQL session. (Bug #13395083) * Fixed handling of errors after authentication for Python v3. (Bug #13364285) Documentation - The documentation is still being developed, and is included in the distribution under the docs/ folder. Reporting Bugs -- We welcome and appreciate your feedback and Bug reports: http://bugs.mysql.com/ Enjoy! On behalf of the MySQL Build Team, Kent Boortz -- Kent Boortz, Release Staff engineer Oracle, The MySQL Team Mobile: +46 76 77 69 049 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.1.42 has been released
master. Now the SQL mode is checked, and the statement is replicated unless strict mode is in effect. For more information, see Section 5.1.8, "Server SQL Modes." (Bug#38173: http://bugs.mysql.com/bug.php?id=38173) See also Bug#38262: http://bugs.mysql.com/bug.php?id=38262, Bug#43992: http://bugs.mysql.com/bug.php?id=43992. * The result of comparison between nullable BIGINT and INT columns was inconsistent. (Bug#49517: http://bugs.mysql.com/bug.php?id=49517) * Incorrect cache initialization prevented storage of converted constant values and could produce incorrect comparison results. (Bug#49489: http://bugs.mysql.com/bug.php?id=49489) * Comparisons involving YEAR values could produce incorrect results. (Bug#49480: http://bugs.mysql.com/bug.php?id=49480) See also Bug#43668: http://bugs.mysql.com/bug.php?id=43668. * If a query involving a table was terminated with KILL, a subsequent SHOW CREATE TABLE for that table caused a server crash. (Bug#48985: http://bugs.mysql.com/bug.php?id=48985) * If the InnoDB tablespace was configured with too small a value, the server could crash and corrupt the tablespace. (Bug#48469: http://bugs.mysql.com/bug.php?id=48469) * Parts of the range optimizer could be initialized incorrectly, resulting in Valgrind errors. (Bug#48459: http://bugs.mysql.com/bug.php?id=48459) * On Windows, InnoDB could not be built as a statically linked library. (Bug#48317: http://bugs.mysql.com/bug.php?id=48317) * mysql_secure_installation did not work on Solaris. (Bug#48086: http://bugs.mysql.com/bug.php?id=48086) * Using REPLACE to update a previously inserted negative value in an AUTO_INCREMENT coumn in an InnoDB table caused the table auto-increment value to be updated to 2147483647. (Bug#47720: http://bugs.mysql.com/bug.php?id=47720) * If a session held a global read lock acquired with FLUSH TABLES WITH READ LOCK, a lock for one table acquired with LOCK TABLES, and issued an INSERT DELAYED statement for another table, deadlock could occur. (Bug#47682: http://bugs.mysql.com/bug.php?id=47682) * The mysql client status command displayed an incorrect value for the server character set. (Bug#47671: http://bugs.mysql.com/bug.php?id=47671) * After a binary upgrade to MySQL 5.1 from a MySQL 5.0 installation that contains ARCHIVE tables, accessing those tables caused the server to crash, even if you had run mysql_upgrade or CHECK TABLE ... FOR UPGRADE. To work around this problem, use mysqldump to dump all ARCHIVE tables before upgrading, and reload them into MySQL 5.1 after upgrading. The same problem occurs for binary downgrades from MySQL 5.1 to 5.0. (Bug#47012: http://bugs.mysql.com/bug.php?id=47012) * The IGNORE clause on a DELETE statement masked an SQL statement error that occurred during trigger processing. (Bug#46425: http://bugs.mysql.com/bug.php?id=46425) * The return value was not checked for some my_hash_insert() calls. (Bug#45613: http://bugs.mysql.com/bug.php?id=45613) * Use of InnoDB monitoring (SHOW ENGINE INNODB STATUS or one of the InnoDB Monitor tables) could cause a server crash due to invalid access to a shared variable in a concurrent environment. This is a further fix for a regression introduced in MySQL 5.1.38 to the original fix in MySQL 5.1.31. (Bug#38883: http://bugs.mysql.com/bug.php?id=38883) * If a comparison involved a constant value that required type conversion, the converted value might not be cached, resulting in repeated conversion and poorer performance. (Bug#34384: http://bugs.mysql.com/bug.php?id=34384) * Using the SHOW ENGINE INNODB STATUS statement when using partitions in InnoDB tables caused Invalid (old?) table or database name errors to be logged. (Bug#32430: http://bugs.mysql.com/bug.php?id=32430) * The Mac OS X 10.6 MySQL preference panel now contains x86 64-bit binaries. (Bug#46935: http://bugs.mysql.com/bug.php?id=46935) Thanks, MySQL RE Team Kent Boortz, Hery Ramilison, Karen Langford, MySQL Release Engineers Database Group, Sun Microsystem Inc. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySQL Community Server 5.1.32 has been released
Dear MySQL users, MySQL Community Server 5.1.32, a new version of the popular Open Source Database Management System, has been released. MySQL 5.1.32 is recommended for use on production systems. For an overview of what's new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html For information on installing MySQL 5.1.32 on new servers or upgrading to MySQL 5.1.32 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html MySQL Server is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ Not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: http://forge.mysql.com/wiki/Contributing For information on open issues in MySQL 5.1, please see the errata list at http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-32.html Sincerely, Kent Boortz The MySQL build team at Sun Microsystems === Functionality added or changed: * Important Change: Replication: RESET MASTER and RESET SLAVE now reset the values shown for Last_IO_Error, Last_IO_Errno, Last_SQL_Error, and Last_SQL_Errno in the output of SHOW SLAVE STATUS. (Bug#34654: http://bugs.mysql.com/34654) * Incompatible Change: The fix for Bug#33699: http://bugs.mysql.com/33699 introduced a change to the UPDATE statement such that assigning NULL to a NOT NULL column caused an error even when strict SQL mode was not enabled. The original behavior before was that such assignments caused an error only in strict SQL mode, and otherwise set the column to the the implicit default value for the column data type and generated a warning. (For information about implicit default values, see Section 10.1.4, "Data Type Default Values.") The change caused compatibility problems for applications that relied on the original behavior. It also caused replication problems between servers that had the original behavior and those that did not, for applications that assigned NULL to NOT NULL columns in UPDATE statements without strict SQL mode enabled. This change has been reverted so that UPDATE again had the original behavior. Problems can still occur if you replicate between servers that have the modified UPDATE behavior and those that do not. (Bug#39265: http://bugs.mysql.com/39265) * The libedit library was upgraded to version 2.11. (Bug#42433: http://bugs.mysql.com/42433) Bugs fixed: * Security Fix: Using an XPath expression employing a scalar expression as a FilterExpr (http://www.w3.org/TR/xpath#NT-FilterExpr) with ExtractValue() or UpdateXML() caused the server to crash. Such expressions now cause an error instead. (Bug#42495: http://bugs.mysql.com/42495) * Replication: START SLAVE UNTIL did not work correctly with --replicate-same-server-id enabled; when started with this option, the slave did not perform events recorded in the relay log and that originated from a different master. Log rotation events are automatically generated and written when rotating the binary log or relay log. Such events for relay logs are usually ignored by the slave SQL thread because they have the same server ID as that of the slave. However, when --replicate-same-server-id was enabled, the rotation event for the relay log was treated as if it originated on the master, because the log's name and position were incorrectly updated. This caused the MASTER_POS_WAIT() function always to return NULL and thus to fail. (Bug#38734: http://bugs.mysql.com/38734, Bug#38934: http://bugs.mysql.com/38934) * Replication: TRUNCATE statements failed to replicate when statement-based binary logging mode was not available. The issue was observed when using InnoDB with the transaction isolation level set to READ UNCOMMITTED (thus forcing InnoDB not to allow statement-based logging). However, the same behavior could be reproduced using any transactional storage engine supporting only row-based logging, regardless of the isolation level. This was due to two separate problems: 1. An error was printed by InnoDB for TRUNCATE when using statement-based logging mode where the transaction isolation level was set to READ COMMITTED or READ UNCOMMITTED, because InnoDB permits statement-based replication for DML statements.
MySQL 6.0.8 Alpha has been released!
Dear MySQL users, MySQL 6.0.8-alpha, a new version of the MySQL database system has been released. The main page for MySQL 6.0 release is at http://www.mysql.com/mysql60/ MySQL 6.0 includes two new storage engines: the transactional Falcon engine, and the crash-safe Maria engine. If you are new to the Falcon storage engine and need more information, please read the Falcon Evaluation Guide at http://www.mysql.com/why-mysql/white-papers/falcon-getting-started.php and the Falcon White Paper at http://www.mysql.com/why-mysql/white-papers/storage-engines-falcon.php The Maria storage engine is a crash safe version of MyISAM. Maria supports all of the main functionality of the MyISAM engine, but includes recovery support (in the event of a system crash), full logging (including CREATE, DROP, RENAME and TRUNCATE operations), all MyISAM row forma ts and a new Maria specific row format. Maria is documented at http://dev.mysql.com/doc/refman/6.0/en/se-maria.html MySQL 6.0.8-alpha is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/mysql/6.0.html and mirror sites. Note that not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, and patches at http://forge.mysql.com/wiki/Contributing The following section lists important, incompatible and security changes since the previous version of MySQL 6.0. The full changelog, including many more fixes can be viewed online at http://dev.mysql.com/doc/refman/6.0/en/news-6-0-8.html Sincerely, Kent Boortz The MySQL build team at Sun Microsystems == Functionality added or changed: * Incompatible Change: The tables for MySQL Backup logging have been renamed, and the logging capabilities now are more flexible, similar to the capabilities provided for the general query log and slow query log. + The names of the MySQL Backup log tables in the mysql database have been changed from 'online_backup' and 'online_backup_progress' to 'backup_history' and 'backup_progress'. + Logging now can be enabled or disabled, it is possible to log to tables or to files, and the names of the log files can be changed. For details, see Section 6.3.3.1, "MySQL Backup Log Control." + A new statement, FLUSH BACKUP LOGS, closes and reopens the backup log files. A new option for mysql_refresh(), REFRESH_BACKUP_LOG, performs the same operation. * Important Change: The '--skip-thread-priority' option is now deprecated in MySQL 5.1 and is removed in MySQL 6.0 such that the server won't change the thread priorities by default. Giving threads different priorities might yield marginal improvements in some platforms (where it actually works), but it might instead cause significant degradation depending on the thread count and number of processors. Meddling with the thread priorities is a not a safe bet as it is very dependent on the behavior of the CPU scheduler and system where MySQL is being run. (Bug#35164: http://bugs.mysql.com/35164, Bug#37536: http://bugs.mysql.com/37536) * Important Change: The '--log' option now is deprecated and will be removed (along with the log system variable) in the future. Instead, use the '--general_log' option to enable the general query log and the '--general_log_file=file_name' option to set the general query log filename. The values of these options are available in the general_log and 'general_log_file' system variables, which can be changed at runtime. Similar changes were made for the '--log-slow-queries' option and 'log_slow_queries' system variable. You should use the '--slow_query_log' and '--slow_query_log_file=file_name' options instead (and the 'slow_query_log' and 'slow_query_log_file' system variables). * The "BUILD/compile-solaris-*" scripts now compile MySQL with the mtmalloc library rather than malloc. (Bug#38727: http://bugs.mysql.com/38727) * BACKUP DATABASE now performs an implicit commit, like RESTORE. (Bug#38261: http://bugs.mysql.com/38261) * The deprecated '--default-table-type' server option has been removed. (Bug#34818: http://bugs.mysql.com/34818) * On WIndows, use of POSIX I/O interfaces in mysys was replaced with Win32 API calls (CreateFile(), WriteFile(), and so forth) and the default maximum number of open files has been increased to 16384. The maximum can be
MySQL 5.1.29-rc has been released
Dear MySQL users, We are proud to present to you the MySQL Server 5.1.29-rc release, a new "release candidate" version of the popular open source database. Bear in mind that this is still a "candidate" release, and as with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. For production level systems using 5.0, we would like to direct your attention to the product description of MySQL Enterprise at: http://mysql.com/products/enterprise/ The MySQL 5.1.29-rc release is now available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ and mirror sites. Note that not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches etc.: http://forge.mysql.com/wiki/Contributing The following section lists the changes from version to version in the MySQL source code since the latest released version of MySQL 5.1, the MySQL 5.1.28-rc release. It can also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-29.html Sincerely, Kent Boortz The MySQL build team at Sun Microsystems === Functionality added or changed: * Important Change: The --skip-thread-priority option is now deprecated in MySQL 5.1 and is removed in MySQL 6.0 such that the server won't change the thread priorities by default. Giving threads different priorities might yield marginal improvements in some platforms (where it actually works), but it might instead cause significant degradation depending on the thread count and number of processors. Meddling with the thread priorities is a not a safe bet as it is very dependent on the behavior of the CPU scheduler and system where MySQL is being run. (Bug#35164: http://bugs.mysql.com/35164, Bug#37536: http://bugs.mysql.com/37536) * Important Change: The --log option now is deprecated and will be removed (along with the log system variable) in the future. Instead, use the --general_log option to enable the general query log and the --general_log_file=file_name option to set the general query log filename. The values of these options are available in the general_log and general_log_file system variables, which can be changed at runtime. Similar changes were made for the --log-slow-queries option and log_slow_queries system variable. You should use the --slow_query_log and --slow_query_log_file=file_name options instead (and the slow_query_log and slow_query_log_file system variables). * The SHOW PROFILES and SHOW PROFILE statements were added to display statement profile data, and the accompanying "INFORMATION_SCHEMA.PROFILING" table. Profiling is controlled via the 'profiling' and 'profiling_history_size' session variables. (Community contribution by Jeremy Cole) * The BUILD/compile-solaris-* scripts now compile MySQL with the mtmalloc library rather than malloc. (Bug#38727: http://bugs.mysql.com/38727) Bugs fixed: * Incompatible Change: Replication: The default binary logging mode has been changed from MIXED to STATEMENT for compatibility with MySQL 5.0. (Bug#39812: http://bugs.mysql.com/39812) * Incompatible Change: In connection with view creation, the server created arc directories inside database directories and maintained useless copies of .frm files there. Creation and renaming procedures of those copies as well as creation of arc directories has been discontinued. This change does cause a problem when downgrading to older server versions which manifests itself under these circumstances: 1. Create a view v_orig in MySQL 5.1.29 or higher. 2. Rename the view to v_new and then back to v_orig. 3. Downgrade to an older 5.1.x server and run mysql_upgrade. 4. Try to rename v_orig to v_new again. This operation fails. As a workaround to avoid this problem, use either of these approaches: + Dump your data using mysqldump before downgrading and reload the dump file after downgrading. + Instead of renaming a view after the downgrade, drop it and recreate it. (Bug#17823: http://bugs.mysql.com/17823) See also Bug#40021: http://bugs.mysql.com/40021 * Important Change: Replication: The SUPER privilege is now required to change the session value of binlog_format as well as its global value. For more information about binlog_format, see Section 15.1.2, "Replication Formats." (Bug#39106: http://bugs.mysql.com/39106) * Partitioning: Replication: Rep
Re: MySQL 5.1.24-rc has been released (part 1 of 2)
Christian Hammers <[EMAIL PROTECTED]> writes: > On Wed, 16 Apr 2008 16:43:01 +0200 > Kent Boortz <[EMAIL PROTECTED]> wrote: > >> >> * Disk Data: Important Change: It is no longer possible on >>32-bit systems to issue statements appearing to create Disk >>Data log files or data files greater than 4 GB in size. >>(Trying to create log files or data files larger than 4 GB on >>32-bit systems led to unrecoverable data node failures; such >>statements now fail with NDB error 1515.) >>(Bug#29186: http://bugs.mysql.com/29186) > > According to the patches I would assume that this only affects people > using the NDB cluster engine but from your notes I would think that > even my old MyISAM tables are affected. > > I do have *.MYD files as big as 15GB on a 32bit system and guess > that I'm not the only one. > > Could you clarify that on the next release notes? Yes, this is only about NDB, but you are right this could have been made more clear. I have forwarded your comment, thanks, kent -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL 5.1.24-rc has been released (part 2 of 2)
they are reported only at routine creation time. (Bug#21801: http://bugs.mysql.com/21801) * Renaming a column that appeared in a foreign key definition did not update that definition with the new column name. This occurred with both referenced and referencing tables. (Bug#21704: http://bugs.mysql.com/21704) * On Mac OS X, mysqld did not react to Ctrl-C when run under gdb, even when run with the --gdb option. (Bug#21567: http://bugs.mysql.com/21567) * CREATE ... SELECT did not always set DEFAULT column values in the new table. (Bug#21380: http://bugs.mysql.com/21380) * mysql_config output did not include -lmygcc on some platforms when it was needed. (Bug#21158: http://bugs.mysql.com/21158) * The BENCHMARK() function, invoked with more than 2147483648 iterations (the size of a signed 32-bit integer), terminated prematurely. (Bug#20752: http://bugs.mysql.com/20752) * MySQLInstanceConfig.exe could lose the innodb_data_home_dir setting when reconfiguring an instance. (Bug#19797: http://bugs.mysql.com/19797) * DROP DATABASE did not drop orphaned FOREIGN KEY constraints. (Bug#18942: http://bugs.mysql.com/18942) * CREATE TABLE allowed 0 as the default value for a TIMESTAMP column when the server was running in NO_ZERO_DATE mode. (Bug#18834: http://bugs.mysql.com/18834) * A SET column whose definition specified 64 elements could not be updated using integer values. (Bug#15409: http://bugs.mysql.com/15409) * If a SELECT calls a stored function in a transaction, and a statement within the function fails, that statement should roll back. Furthermore, if ROLLBACK is executed after that, the entire transaction should be rolled back. Before this fix, the failed statement did not roll back when it failed (even though it might ultimately get rolled back by a ROLLBACK later that rolls back the entire transaction). (Bug#12713: http://bugs.mysql.com/12713) See also Bug#34655: http://bugs.mysql.com/34655 * The parser incorrectly allowed SQLSTATE '0' to be specified for a condition handler. (This is incorrect because the condition must be a failure condition and '0' indicates success.) (Bug#8759: http://bugs.mysql.com/8759) -- Kent Boortz, Senior Production Engineer Sun Microsystems Office: +46 19 182931 Mobile: +46 70 2791171 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL 5.1.24-rc has been released (part 1 of 2)
Dear MySQL users, We are proud to present to you the MySQL Server 5.1.24-rc release, a new "release candidate" version of the popular open source database. Bear in mind that this is still a "candidate" release, and as with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. For production level systems using 5.0, we would like to direct your attention to the product description of MySQL Enterprise at: http://mysql.com/products/enterprise/ The MySQL 5.1.24-rc release is now available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ and mirror sites. Note that not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. Please also note that some of our mirrors are currently experiencing problems that may result in serving corrupted files. We are working with the mirror maintainers to resolve this. We welcome and appreciate your feedback, bug reports, bug fixes, patches etc.: http://forge.mysql.com/wiki/Contributing The description of the changes from version 5.1.23-rc to this 5.1.24-rc is some 1,800 lines long, that is about 96 kB. As some mail systems are bound to truncate long mail at 64 kB, I split the announcement into two parts - this is part 1 only. The following section lists the (first part of the) changes from version to version in the MySQL source code since the latest released version of MySQL 5.1, the MySQL 5.1.23-rc release. It can also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-24.html Sincerely, Kent Boortz The MySQL build team at Sun Microsystems == Functionality added or changed: * Please note that the Federated engine is not built into the MySQL 5.1.24 RC release binaries, but is scheduled to return in the next release, which will be MySQL 5.1.25. The reasons for Federated's omission in 5.1.24 RC includes various quality and timing issues that unfortunately could not be avoided, and we apologize for any inconvenience this has caused. * Windows Installer: Important Change: The data directory now defaults to the Windows Common App Data Folder (on Windows XP, this is ...\All Users\Application Data; on Vista, it is ProgramData). (Bug#34593: http://bugs.mysql.com/34593) * Cluster API: Important Change: Because NDB_LE_MemoryUsage.page_size_kb shows memory page sizes in bytes rather than kilobytes, it has been renamed to page_size_bytes. The name page_size_kb is now deprecated and thus subject to removal in a future release, although it currently remains supported for reasons of backwards compatibility. See The Ndb_logevent_type Type (http://dev.mysql.com/doc/ndbapi/en/ndb-logevent-type.html), for more information about NDB_LE_MemoryUsage. (Bug#30271: http://bugs.mysql.com/30271) * Replication: Introduced the slave_exec_mode system variable to control whether idempotent or strict mode is used for replication conflict resolution. Idempotent mode suppresses duplicate-key, no-key-found, and some other errors, and is needed for circular replication, multi-master replication, and some other complex replication setups when using MySQL Cluster. Strict mode is the default. (Bug#31609: http://bugs.mysql.com/31609) * Replication: When running the server with --binlog-format=MIXED or --binlog-format=STATEMENT, a query that referred to a system variable used the slave's value when replayed on the slave. This meant that, if the value of a system variable was inserted into a table, the slave differed from the master. Now, statements that refer to a system variable are marked as "unsafe", which means that: + When the server is using --binlog-format=MIXED, the row-based format is used automatically to replicate these statements. + When the server is using --binlog-format=STATEMENT, these statements produce a warning. (Bug#31168: http://bugs.mysql.com/31168) See also Bug#34732: http://bugs.mysql.com/34732 * The ndbd and ndb_mgmd manpages have been reclassified from volume 1 to volume 8. (Bug#34642: http://bugs.mysql.com/34642) * For binary .tar.gz packages, mysqld and other binaries now are compiled with debugging symbols included to enable easier use with a debugger. (Bug#33252: http://bugs.mysql.com/33252) * Formerly, when the MySQL server crashed, the generated stack dump was numeric and required external tools to properly resolve the names of functions. This is not very helpful to users having a limited knowledge of debugging techniques. In addition, the generated stack trace contained only the names of functions and was form
MySQL 4.0.27 has been released - Security Update
CREATE ... SELECT could cause a server crash. (Bug#12845: http://bugs.mysql.com/12845) * On HP-UX 11.x (PA-RISC), the -L option caused "mysqlimport" to crash. (Bug#12958: http://bugs.mysql.com/12958) * The server crashed when one thread resized the query cache while another thread was using it. (Bug#12848: http://bugs.mysql.com/12848) Bugs fixed (for problems building from source): * Avoid trying to include when it doesn't work in C++ code. (Bug#13621: http://bugs.mysql.com/13621) * MySQL would not compile on Linux distributions that use the "tinfo" library. (Bug#18912: http://bugs.mysql.com/18912) * Fixed problems with static variables to allow building on Fedora Core 3. (Bug#6554: http://bugs.mysql.com/6554) kent -- Kent Boortz, Senior Software Developer MySQL AB, www.mysql.com Office: +46 18 174400 ext. 4450 (VoIP) Office: +46 19 182931 Mobile: +46 70 2791171 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL 5.1.6-alpha has been released
same partitioned table would cause the server to crash. (Bug#13442 (http://bugs.mysql.com/13442)) * Using a REPLACE statement on a partitioned table caused the server to crash. (Bug#13440 (http://bugs.mysql.com/13440)) * Using an identifier rather than a literal integer value in the LESS THAN clause of a range-partitioned table could cause the server to crash and corruption of tables. (Bug#13439 (http://bugs.mysql.com/13439)) * Using ENGINE=... within a PARTITION clause could cause the server to crash. (Bug#13438 (http://bugs.mysql.com/13438)) * CREATE TABLE ... LIKE did not work if the table whose schema was to be copied was a partitioned table. (Bug#13435 (http://bugs.mysql.com/13435)) * SHOW CREATE TABLE did not display the PARTITIONS clause for tables partitioned by HASH or KEY. (Bug#14327 (http://bugs.mysql.com/14327)) * Certain permission management statements could create a NULL hostname for a user, resulting in a server crash. (Bug#15598 (http://bugs.mysql.com/15598)) * Temporary table aliasing did not work inside stored functions. (Bug#12198 (http://bugs.mysql.com/12198)) * Parallel builds occasionally failed on Solaris. (Bug#16282 (http://bugs.mysql.com/16282)) Enjoy, kent -- Kent Boortz, Senior Software Developer MySQL AB, www.mysql.com Office: +46 18 174400 ext. 4450 (VoIP) Office: +46 19 182931 Mobile: +46 70 2791171 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL 4.1.18 has been released
RGE set can return errors when statement involves insert into child table from merge table or vice-versa. (Bug#5390 (http://bugs.mysql.com/5390)) * Certain permission management statements could create a NULL hostname for a user, resulting in a server crash. (Bug#15598 (http://bugs.mysql.com/15598)) * For InnoDB tables, using a column prefix for a utf8 column in a primary key caused Cannot find record errors when attempting to locate records. (Bug#14056 (http://bugs.mysql.com/14056)) * Certain CREATE TABLE ... AS ... statements involving ENUM columns could cause server crash. (Bug#12913 (http://bugs.mysql.com/12913)) * Using an aggregate function as the argument for a HAVING clause would result in the aggregate function always returning FALSE. (Bug#14274 (http://bugs.mysql.com/14274)) * The COALESCE() function truncated data in a TINYTEXT column. (Bug#15581 (http://bugs.mysql.com/15581)) * InnoDB: Comparison of indexed VARCHAR CHARACTER SET ucs2 COLLATE ucs2_bin columns using LIKE could fail. (Bug#14583 (http://bugs.mysql.com/14583)) * Issuing a DROP USER command could cause some users to encounter a hostname is not allowed to connect to this MySQL server error. (Bug#15775 (http://bugs.mysql.com/15775)) * Access Denied error could be erroneously returned with specific grant combinations under high load. (Bug#7209 (http://bugs.mysql.com/7209)) * Symbolic links did not function properly on Windows platforms. (Bug#14960 (http://bugs.mysql.com/14960), Bug#14310 (http://bugs.mysql.com/14310)) * BDB: A DELETE, INSERT, or UPDATE of a BDB table could cause the server to crash where the query contained a subquery using an index read. (Bug#15536 (http://bugs.mysql.com/15536)) * DELETE could report full-text index corruption (Invalid key for table ...) if the index was built with repair-by-sort, the data in the full-text index used UCA collation, and some word appeared in the data terminated by a 0xC2A0 character as well as by other non-letter characters. (Bug#11336 (http://bugs.mysql.com/11336)) * A race condition when creating temporary files caused a deadlock on Windows with threads in Opening tables or Waiting for table states. (Bug#12071 (http://bugs.mysql.com/12071)) * InnoDB: If FOREIGN_KEY_CHECKS was 0, InnoDB allowed inconsistent foreign keys to be created. (Bug#13778 (http://bugs.mysql.com/13778)) * NDB Cluster: A memory leak occurred when performing ordered index scans using indexes a columns larger than 32 bytes, which would eventually lead to the forced shutdown of all mysqld server processes used with the cluster. (Bug#13078 (http://bugs.mysql.com/13078)) * NDB Cluster: Under some circumstances, it was possible for a restarting node to undergo a forced shutdown. (Bug#15632 (http://bugs.mysql.com/15632)) * NDB Cluster: If an abort by the Transaction Coordinator timed out, the abort condition was incorrectly handled, causing the transacviton record to be released prematurely. (Bug#15685 (http://bugs.mysql.com/15685)) * NDB Cluster: A node which failed during cluster startup was sometimes not removed from the internal list of active nodes. (Bug#15587 (http://bugs.mysql.com/15587)) * NDB Cluster: There was a small window for a node failure to occur during a backup without an error being reported. (Bug#15425 (http://bugs.mysql.com/15425)) * Multiple-table update operations were counting updates and not updated rows. As a result, if a row had several updates it was counted several times for the "rows matched" value but updated only once. (Bug#15028 (http://bugs.mysql.com/15028)) * SELECT queries that began with an opening parenthesis were not being placed in the query cache. (Bug#14652 (http://bugs.mysql.com/14652)) kent -- Kent Boortz, Senior Software Developer MySQL AB, www.mysql.com Office: +46 18 174400 ext. 4450 (VoIP) Office: +46 19 182931 Mobile: +46 70 2791171 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
