How to get the MySQL Command-Line Tool to display Unicode properly

2017-10-18 Thread Roger House 
I use a Python program to write text containing Unicode characters to a 
MySQL

database.  As an example, two of the characters are

    u'\u2640' a symbol for Venus or female
    u'\u2642' a symbol for Mars or male

I use utf8mb4 for virtually all character sets involved with MySQL.  Here is
an excerpt from /etc/mysql/my.cnf

    [client]
    default-character-set=utf8mb4

    [mysql]
    default-character-set=utf8mb4

    [mysqld]
    character-set-server =utf8mb4

I'm not sure that the [client] option does anything, but it doesn't seem to
hurt.

In addition, all tables are created with these parameters:

    ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci

In all respects except one, the treatment of Unicode works just fine.  I can
write Unicode to database tables, read it, display it, etc., with no
problems.  The exception is mysql, the MySQL Command-Line Tool.  When I
execute a SELECT statement to see rows in a table containing the Venus and
Mars Unicode characters, here is what I see on the screen:

    | Venus | ♀  |
    | Mars  | ♂  |

What I want to see is this

    | Venus | ♀  |
    | Mars  | ♂  |

I get the same behavior with the MySQL Command Line Tool when I run it on
Windows, Mac OS X, and Ubuntu, so I'm pretty sure the problem has to do 
with

mysql itself.

Any ideas about how to get the MySQL Command-Line Tool to display Unicode
properly?

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Cluster 7.3.19 has been released

2017-10-18 Thread Prashant Tekriwal 

Dear MySQL Users,

MySQL Cluster is the distributed, shared-nothing variant of MySQL.
This storage engine provides:

  - In-Memory storage - Real-time performance (with optional
checkpointing to disk)
  - Transparent Auto-Sharding - Read & write scalability
  - Active-Active/Multi-Master geographic replication

  - 99.999% High Availability with no single point of failure
and on-line maintenance
  - NoSQL and SQL APIs (including C++, Java, http, Memcached
and JavaScript/Node.js)

MySQL Cluster 7.3.19, has been released and can be downloaded from

http://www.mysql.com/downloads/cluster/

where you will also find Quick Start guides to help you get your
first MySQL Cluster database up and running.

The release notes are available from

http://dev.mysql.com/doc/relnotes/mysql-cluster/7.3/en/index.html

MySQL Cluster enables users to meet the database challenges of next
generation web, cloud, and communications services with uncompromising
scalability, uptime and agility.

More details can be found at

http://www.mysql.com/products/cluster/

Enjoy !

== 

Changes in MySQL NDB Cluster 7.3.19 (5.6.38-ndb-7.3.19) (2017-10-18, 
General Availability)


   MySQL NDB Cluster 7.3.19 is a new release of NDB Cluster,
   based on MySQL Server 5.6 and including features from version
   7.3 of the NDB storage engine, as well as fixing a number of
   recently discovered bugs in previous NDB Cluster releases.

   Obtaining MySQL NDB Cluster 7.3.  MySQL NDB Cluster 7.3
   source code and binaries can be obtained from
http://dev.mysql.com/downloads/cluster/.

   For an overview of changes made in MySQL NDB Cluster 7.3, see
   What is New in NDB Cluster 7.3
(http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-3.html). 



   This release also incorporates all bug fixes and changes made
   in previous NDB Cluster releases, as well as all bug fixes and
   feature changes which were added in mainline MySQL 5.6
   through MySQL 5.6.38 (see Changes in MySQL 5.6.38 (Not yet
   released, General Availability)
(http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-38.html)).

   Bugs Fixed

 * Added DUMP code 7027 to facilitate testing of issues
   relating to local checkpoints. For more information, see
   DUMP 7027
(http://dev.mysql.com/doc/ndb-internals/en/ndb-internals-dump-command-7027.html). 
(Bug #26661468)


 * A previous fix intended to improve logging of node
   failure handling in the transaction coordinator included
   logging of transactions that could occur in normal
   operation, which made the resulting logs needlessly
   verbose. Such normal transactions are no longer written
   to the log in such cases. (Bug #26568782)
   References: This issue is a regression of: Bug #26364729.

 * Some DUMP codes used for the LGMAN kernel block were
   incorrectly assigned numbers in the range used for codes
   belonging to DBTUX. These have now been assigned symbolic
   constants and numbers in the proper range (10001, 10002,
   and 10003). (Bug #26365433)

 * Node failure handling in the DBTC kernel block consists
   of a number of tasks which execute concurrently, and all
   of which must complete before TC node failure handling is
   complete. This fix extends logging coverage to record
   when each task completes, and which tasks remain,
   includes the following improvements:

  + Handling interactions between GCP and node failure
handling interactions, in which TC takeover causes
GCP participant stall at the master TC to allow it
to extend the current GCI with any transactions that
were taken over; the stall can begin and end in
different GCP protocol states. Logging coverage is
extended to cover all scenarios. Debug logging is
now more consistent and understandable to users.

  + Logging done by the QMGR block as it monitors
duration of node failure handling duration is done
more frequently. A warning log is now generated
every 30 seconds (instead of 1 minute), and this now
includes DBDIH block debug information (formerly
this was written separately, and less often).

  + To reduce space used, DBTC instance number: is
shortened to DBTC number:.

  + A new error code is added to assist testing.
   (Bug #26364729)

 * A potential hundredfold signal fan-out when sending a
   START_FRAG_REQ signal could lead to a node failure due to
   a job buffer full error in start phase 5 while trying to
   perform a local checkpoint during a restart. (Bug #86675,
   Bug #26263397)
   References: See also: Bug #26288247, Bug #26279522.

On Behalf of Oracle/MySQL Release Engineering
Prashant Tekriwal

MySQL Cluster 7.4.17 has been released

2017-10-18 Thread daniel . horecki 

Dear MySQL Users,

MySQL Cluster is the distributed, shared-nothing variant of MySQL.
This storage engine provides:

  - In-Memory storage - Real-time performance
  - Transparent Auto-Sharding - Read & write scalability
  - Active-Active/Multi-Master geographic replication
  - 99.999% High Availability with no single point of failure
    and on-line maintenance
  - NoSQL and SQL APIs (including C++, Java, http, Memcached
    and JavaScript/Node.js)

MySQL Cluster 7.4 makes significant advances in performance;
operational efficiency (such as enhanced reporting and faster restarts
and upgrades) and conflict detection and resolution for active-active
replication between MySQL Clusters.

MySQL Cluster 7.4.17, has been released and can be downloaded from

http://www.mysql.com/downloads/cluster/

where you will also find Quick Start guides to help you get your
first MySQL Cluster database up and running.

The release notes are available from

http://dev.mysql.com/doc/relnotes/mysql-cluster/7.4/en/index.html

MySQL Cluster enables users to meet the database challenges of next
generation web, cloud, and communications services with uncompromising
scalability, uptime and agility.

More details can be found at

http://www.mysql.com/products/cluster/

Enjoy !

Changes in MySQL NDB Cluster 7.4.17 (5.6.38-ndb-7.4.17) (2017-10-18,
General Availability)

   MySQL NDB Cluster 7.4.17 is a new release of MySQL NDB
   Cluster 7.4, based on MySQL Server 5.6 and including features
   in version 7.4 of the NDB storage engine, as well as fixing
   recently discovered bugs in previous NDB Cluster releases.

   Obtaining MySQL NDB Cluster 7.4.  MySQL NDB Cluster 7.4
   source code and binaries can be obtained from
http://dev.mysql.com/downloads/cluster/.

   For an overview of changes made in MySQL NDB Cluster 7.4, see
   What is New in NDB Cluster 7.4
(http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is 
-new-7-4.html 
).


   This release also incorporates all bugfixes and changes made
   in previous NDB Cluster releases, as well as all bugfixes and
   feature changes which were added in mainline MySQL 5.6
   through MySQL 5.6.38 (see Changes in MySQL 5.6.38 (2017-10-16, 
General Availability)
(http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-38 
.html 
).


   Bugs Fixed

 * Added DUMP code 7027 to facilitate testing of issues
   relating to local checkpoints. For more information, see
   DUMP 7027
(http://dev.mysql.com/doc/ndb-internals/en/ndb-internals 
-dump-command-7027.html 
).


   (Bug #26661468)

 * A previous fix intended to improve logging of node
   failure handling in the transaction coordinator included
   logging of transactions that could occur in normal
   operation, which made the resulting logs needlessly
   verbose. Such normal transactions are no longer written
   to the log in such cases. (Bug #26568782)
   References: This issue is a regression of: Bug #26364729.

 * Some DUMP codes used for the LGMAN kernel block were
   incorrectly assigned numbers in the range used for codes
   belonging to DBTUX. These have now been assigned symbolic
   constants and numbers in the proper range (10001, 10002,
   and 10003). (Bug #26365433)

 * Node failure handling in the DBTC kernel block consists
   of a number of tasks which execute concurrently, and all
   of which must complete before TC node failure handling is
   complete. This fix extends logging coverage to record
   when each task completes, and which tasks remain,
   includes the following improvements:

  + Handling interactions between GCP and node failure
    handling interactions, in which TC takeover causes
    GCP participant stall at the master TC to allow it
    to extend the current GCI with any transactions that
    were taken over; the stall can begin and end in
    different GCP protocol states. Logging coverage is
    extended to cover all scenarios. Debug logging is
    now more consistent and understandable to users.

  + Logging done by the QMGR block as it monitors
    duration of node failure handling duration is done
    more frequently. A warning log is now generated
    every 30 seconds (instead of 1 minute), and this now
    includes DBDIH block debug information (formerly
    this was written separately, and less often).

  + To reduce space used, DBTC instance number: is
   

MySQL Cluster 7.5.8 has been released

2017-10-18 Thread Lars Tangvald 

Dear MySQL Users,

MySQL Cluster is the distributed, shared-nothing variant of MySQL.
This storage engine provides:

  - In-Memory storage - Real-time performance (with optional
checkpointing to disk)
  - Transparent Auto-Sharding - Read & write scalability
  - Active-Active/Multi-Master geographic replication

  - 99.999% High Availability with no single point of failure
and on-line maintenance
  - NoSQL and SQL APIs (including C++, Java, http, Memcached
and JavaScript/Node.js)

MySQL Cluster 7.5.8, has been released and can be downloaded from

  http://www.mysql.com/downloads/cluster/

where you will also find Quick Start guides to help you get your
first MySQL Cluster database up and running.

MySQL Cluster 7.5 is also available from our repository for Linux
platforms, go here for details:

  http://dev.mysql.com/downloads/repo/

The release notes are available from

  http://dev.mysql.com/doc/relnotes/mysql-cluster/7.5/en/index.html

MySQL Cluster enables users to meet the database challenges of next
generation web, cloud, and communications services with uncompromising
scalability, uptime and agility.

More details can be found at

  http://www.mysql.com/products/cluster/

Enjoy !


Changes in MySQL NDB Cluster 7.5.8 (5.7.20-ndb-7.5.8) (2017-10-18,
General Availability)

   MySQL NDB Cluster 7.5.8 is a new release of MySQL NDB Cluster
   7.5, based on MySQL Server 5.7 and including features in
   version 7.5 of the NDB
   (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html)
   storage engine, as well as fixing recently discovered bugs in
   previous NDB Cluster releases.

   Obtaining MySQL NDB Cluster 7.5.  MySQL NDB Cluster 7.5
   source code and binaries can be obtained from
   http://dev.mysql.com/downloads/cluster/.

   For an overview of changes made in MySQL NDB Cluster 7.5, see
   What is New in NDB Cluster 7.5
(http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new-7-5.html).

   This release also incorporates all bugfixes and changes made
   in previous NDB Cluster releases, as well as all bugfixes and
   feature changes which were added in mainline MySQL 5.7
   through MySQL 5.7.20 (see Changes in MySQL 5.7.20 (Not yet
   released, General Availability)
(http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-20.html)).

   Bugs Fixed

 * Replication: With GTIDs generated for incident log
   events, MySQL error code 1590 (ER_SLAVE_INCIDENT) could
   not be skipped using the --slave-skip-errors=1590 startup
   option on a replication slave. (Bug #26266758)

 * Errors in parsing NDB_TABLE modifiers could cause memory
   leaks. (Bug #26724559)

 * Added DUMP code 7027 to facilitate testing of issues
   relating to local checkpoints. For more information, see
   DUMP 7027
(http://dev.mysql.com/doc/ndb-internals/en/ndb-internals-dump-command-7027.html). 
(Bug #26661468)


 * A previous fix intended to improve logging of node
   failure handling in the transaction coordinator included
   logging of transactions that could occur in normal
   operation, which made the resulting logs needlessly
   verbose. Such normal transactions are no longer written
   to the log in such cases. (Bug #26568782)
   References: This issue is a regression of: Bug #26364729.

 * Due to a configuration file error, CPU locking capability
   was not available on builds for Linux platforms. (Bug
   #26378589)

 * Some DUMP codes used for the LGMAN kernel block were
   incorrectly assigned numbers in the range used for codes
   belonging to DBTUX. These have now been assigned symbolic
   constants and numbers in the proper range (10001, 10002,
   and 10003). (Bug #26365433)

 * Node failure handling in the DBTC kernel block consists
   of a number of tasks which execute concurrently, and all
   of which must complete before TC node failure handling is
   complete. This fix extends logging coverage to record
   when each task completes, and which tasks remain,
   includes the following improvements:

  + Handling interactions between GCP and node failure
handling interactions, in which TC takeover causes
GCP participant stall at the master TC to allow it
to extend the current GCI with any transactions that
were taken over; the stall can begin and end in
different GCP protocol states. Logging coverage is
extended to cover all scenarios. Debug logging is
now more consistent and understandable to users.

  + Logging done by the QMGR block as it monitors
duration of node failure handling duration is done
more frequently. A warning log is now generated
every 30 seconds (instead of 1 minute), and this now
includes DBDIH block debug information (formerly
this was written separately, and less often).

  + To reduce