MySQL Community Server 5.7.6 has been released (part 3/3)
[This is part 3 (last) of the announcement ] * Partitioning: When multiple columns are used in KEY partitioning, their order may help determine the partition in which the row is placed. Changing this order by means of an ALTER TABLE that uses ALGORITHM=INPLACE can lead to inconsistency when placing rows in partitions; in other words, a row inserted before such an operation operation is placed in one partition, but the same row inserted afterwards is placed in a different one. For this reason, altering the order of a multicolumn index online is no longer allowed when that index is also used as the base for partitioning the table by KEY; instead, you must use a copying ALTER TABLE to perform the change. (Bug #17896265) * Replication: When enforce_gtid_consistency was set to WARN, if a second GTID consistency violating statement within a transaction was encountered, it was not raising a warning. This was due to the fact that by design the transaction context was marked as GTID violating, hence no other warnings were being issued until the transaction committed. The fix ensures that a warning is raised for all statements inside a transaction correctly. (Bug #20414559) * Replication: After restarting a slave, the first relay log was missing the Previous_gtids log event. Since MySQL version 5.7.6, a Previous_gtids log event is added to every log. This fix ensures that a Previous_gtids log event is correctly added to the first relay log. (Bug #20106390) * Replication: When purging binary logs and the first left binary log contained only a Previous_gtids log event, a lost_gtids-is_empty() assertion was caused. This was related to the fix for Bug#16741603 and has now been corrected. (Bug #20075721) * Replication: When using a slave configured to use a special character set such as UTF-16, UTF-32, or UCS-2, the receiver (I/O) thread failed to connect. The fix ensures that in such a situation, if a slave's character set is not supported then default to using the latin1 character set. (Bug #19855907) * Replication: If a client thread on a slave executed FLUSH TABLES WITH READ LOCK while the master executed a DML, executing SHOW SLAVE STATUS in the same client became blocked, causing a deadlock. The fix ensures that the read lock is only held during the period that the relay log is being updated and the deadlock is avoided. (Bug #19843808) * Replication: When using multi-source replication with multiple channels and with a multi-threaded slave enabled, resetting the slave and then executing RESET SLAVE ALL, START SLAVE or STOP SLAVE resulted in a crash. This has now been fixed and the multi-threaded slave can be restarted in a multi-source replication setup. (Bug #19784641) * Replication: The CHANGE REPLICATION FILTER statement can be used to create an empty filter, for example when clearing previously configured replication filters. This caused a crash in previous versions when creating an empty filter for REPLICATE_DO_TABLE, REPLICATE_IGNORE_TABLE, REPLICATE_WILD_DO_TABLE, or REPLICATE_WILD_IGNORE_TABLE. This fix ensures that these replication filters can be safely cleared by setting the filter to be empty. (Bug #19711674) * Replication: When using a MySQL version that had been compiled with the WITH_DEBUG option enabled, using expire_logs_days to purge binary logs caused a restart to crash the server. This problem arose after the fix for Bug #17283409. The fix ensures that current_thd is checked before calling DEBUG_SYNC(). (Bug #19553099) * Replication: When using a multi-threaded slave, the slave receiver (SQL) thread stopped with an ER_MTS_CANT_PARALLEL error when issuing a LOAD DATA INFILE statement that tried to load data into a non-transactional table on the master but failed, for example due to a primary key violation. This was caused by the multi-threaded slave applier incorrectly handling DELETE_FILE events. The fix ensures that a multi-threaded slave handles DELETE_FILE events correctly. (Bug #19552923) * Replication: Sometimes the slave I/O thread leaves a partial group in the current relay log, for example when it is killed or stopped. After it is restarted, a new relay log is created on rotation and a pair of ROTATE_EVENT and FORMAT_DESCRIPTION_EVENT is replicated from master and written into the new relay log. When using a multi-threaded slave, problems such as error 1755 were encountered when applying the remaining part
MySQL Community Server 5.7.6 has been released (part 2/3)
[This is part 2 of the announcement ] * The minimum value of the stored_program_cache system variable has been changed from 256 to 16, to enable configuration of a smaller amount of memory devoted to the stored program cache. (Bug #72451, Bug #18661573) * The code in my_strnxfrm_simple() was suboptimal and was improved. Thanks to Alexey Kopytov for the patch. (Bug #68476, Bug #16403708) * Features have been added to MySQL 5.7.6 which are reserved for future use. These specific changes were implemented: The following errors were added: + ER_BEFORE_DML_VALIDATION_ERROR + ER_PREVENTS_VARIABLE_WITHOUT_RBR + ER_RUN_HOOK_ERROR + ER_TRANSACTION_ROLLBACK_DURING_COMMIT + ER_GROUP_REPLICATION_CONFIGURATION + ER_GROUP_REPLICATION_RUNNING + ER_GROUP_REPLICATION_APPLIER_INIT_ERROR + ER_GROUP_REPLICATION_STOP_APPLIER_THREAD_TIMEOUT + ER_GROUP_REPLICATION_COMMUNICATION_LAYER_SESSION_ERR OR + ER_GROUP_REPLICATION_COMMUNICATION_LAYER_JOIN_ERROR The following Performance Schema tables were added: + replication_group_members + replication_group_member_stats Additionally, the GROUP_NAME variable was added to the replication_connection_status table. The variable transaction_write_set_extraction was added. The following SQL statements were added: + START GROUP_REPLICATION + STOP GROUP_REPLICATION * The following items are deprecated and will be removed in a future MySQL release. Where alternatives are shown, applications should be updated to use them. + The ENCRYPT(), DES_ENCRYPT(), and DES_DECRYPT() functions. Consider using AES_ENCRYPT() and AES_DECRYPT() instead. + The sync_frm system variable. This variable will be removed when .frm files become obsolete. + The global character_set_database and collation_database system variables are deprecated and will be removed in a future version of MySQL. Assigning a value to the session character_set_database and collation_database system variables is deprecated and assignments produce a warning. The session variables will become read only in a future version of MySQL and assignments will produce an error. It will remain possible to access the session variables to determine the database character set and collation for the default database. + Conversion of pre-MySQL 5.1 database names containing special characters to 5.1 format with the addition of a #mysql50# prefix. (For information about these conversions, see Mapping of Identifiers to File Names (http://dev.mysql.com/doc/refman/5.7/en/identifier-mapping.html).) Because such conversions now are deprecated, the --fix-db-names and --fix-table-names options for mysqlcheck and the UPGRADE DATA DIRECTORY NAME clause for the ALTER DATABASE statement are also deprecated. Upgrades are supported only from one major version to another (for example, 5.0 to 5.1, or 5.1 to 5.5), so there should be little remaining need for conversion of older 5.0 database names to current versions of MySQL. As a workaround, upgrade a MySQL 5.0 installation to MySQL 5.1 before upgrading to a more recent release. * For queries that combine ORDER BY with LIMIT, the optimizer may switch to an index that applies to the ORDER BY. In some cases, the decision to switch was based on a heuristic rather than on cost. The optimizer now uniformly makes the decision whether to switch on a cost basis. This should result in better performanance when switching would cause a query to read an entire index or a large part of it to find qualifying rows. References: See also Bug #73837, Bug #19579507, Bug #16522053. * The variable session_track_gtids was added, which enables a tracker that captures GTIDs and appends them to the OK packet. * The plugin and servers tables in the mysql system database now are InnoDB (transactional) tables. Previously, these were MyISAM (nontransactional) tables. In consequence of this change, INSTALL PLUGIN and UNINSTALL PLUGIN are now included among the statements that cause an implicit commit (see Statements That Cause an Implicit Commit (http://dev.mysql.com/doc/refman/5.7/en/implicit-commit.html)). If you upgrade to this release of MySQL from an earlier version, you must run mysql_upgrade (and
Re: ssh basics
On Mon, 9 Mar 2015, Johan De Meersman wrote: I'm interested in how ssh is used by MySQL. SSH is not used by MySQL at all :-) SSH is a way of connecting to a remote machine. MySQL is a database. You can use SSH to do things with the database, but they're not intrinsically related. True, howewer the OP might be interested knowing that I do continuously work on a mysql astronomical database on a different machine A (here on my institute LAN) from MY machine B just opening an xterm in which I ssh to such machine A, and then run the line-mode mysql client on such machine A. We do not offer mysql client access to such database outside of our institute, and in general not even to machines in our institute. For that we have a java tomcat client which connects via JDBC to the database. Since tomcat and mysqld run on the same machine A, we grant access only to a single user on localhost. Conversely, I have some private databases on my machine B. While I maintain them locally with full access, I grant select access to an user on another machine C. In this case he runs the mysql client on C which connects to the mysqld on my machine B (actually he runs shell scripts which do it). I guess all this very simple arrangements should cover the needs of the OP as they do for me. I may like a way to have a program (namely RSI IDL) to connect (bypassing the line mode mysql client) to the mysqld socket and issuing commands to it (essentially I want to issue a select into a table, and read back the output in an IDL structure) but I never managed to do it. But I did not try hard. -- Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html Do not like Firefox =29 ? Get Pale Moon ! http://www.palemoon.org -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: ssh basics
- Original Message - From: Lucio Chiappetti lu...@lambrate.inaf.it I may like a way to have a program (namely RSI IDL) to connect (bypassing the line mode mysql client) to the mysqld socket and issuing commands to it (essentially I want to issue a select into a table, and read back the output in an IDL structure) but I never managed to do it. But I did not try hard. The unix socket, just like a tcp socket, is an appendage of the mysql daemon, and would thus require you to speak the mysql protocol. You can point the appropriate driver for your application to the socket file in roughly the same way as you point it to an ip/port combo (see the driver's documentation); or you can tell the commandline client to execute the query you want using the -e parameter, and optionally -b, -s or a number of others that modify the output format. Sometimes the simplest things work best :-) -- Unhappiness is discouraged and will be corrected with kitten pictures. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: ssh basics
Am 10.03.2015 um 19:06 schrieb Lucio Chiappetti: I guess all this very simple arrangements should cover the needs of the OP as they do for me. but that won't help as long the OP fires up blindly ssh-tunnel commands without understanding what a SSH tunnel and a TCP connection is and *that* is the whole problem of the thread from the frist start: missing basics and follow howtos not understanding what they are talking about signature.asc Description: OpenPGP digital signature
Re: Create Schema and repeatable import of XML
You can have a look at XMLPipeDB. http://sourceforge.net/projects/xmlpipedb/ Iñigo On 03/09, Sayth Renshaw wrote: Hi Hoping someone can help me work some information or direction to a good resource for using XML with Mysql. Specifically I have a complex XML file, I would like to create a schema in MYSQL based on it (I have XSD as well) and be able to upload new xml data into the database as it's released to me. I cannot find a good way to achieve this, currently I am trying to use mysql for excel and map via excel into mysql. The data format is complex and a bit beyond scope of excel. Are there good resources that how to work with XML? Google searches don't show much but confusion and referral to expensive software such as XMLspy. If xml was supposed to be a universal format why is it so hard to work with. Sayth. pgpzWxCo3cswL.pgp Description: PGP signature
