The MySQL Development team is proud to announce version 8.0.20 of the MySQL Shell, with the following features:
… Facebook Twitter LinkedIn
As you know, today, MySQL 8.0.20 has been released. I started this new thread category with 8.0.19 (see this post).
A late thanks to Guoji Ma, for a contribution to bug #95801 “show create table output can’t be executed” that was used as inspiration for the actual fix that was pushed in MySQL 8.0.18.
MySQL 8.0.20, includes contributions from Daniel Black, Cai Yibo, Jericho Rivera, Matti Sillanpää, Nick Pollett, Bruce Feng, Kamil Holubicky, Facebook.
Thank you all for your great contributions. MySQL is an Open Source project, GPL, and we accept contribution of course. Sometimes it’s also good to remind it
Here is the list of the contributions above:
MySQL provides password-reuse capability, which allows database administrators to determine the number of unique passwords a user must use before they can use an old password again.
The post MySQL Security - Password Reuse Policy first appeared on dasini.net - Diary of a MySQL expert.
Dear MySQL users,
MySQL Connector/Python 8.0.20 is the latest GA release version of the
MySQL Connector Python 8.0 series. The X DevAPI enables application
developers to write code that combines the strengths of the relational
and document models using a modern, NoSQL-like syntax that does not
assume previous experience writing traditional SQL.
To learn more about how to write applications using the X DevAPI, see
http://dev.mysql.com/doc/x-devapi-userguide/en/
…
Dear MySQL users,
MySQL Connector/C++ 8.0.20 is a new release version of the MySQL
Connector/C++ 8.0 series.
Connector/C++ 8.0 can be used to access MySQL implementing Document
Store or in a traditional way, using SQL queries. It allows writing
both C++ and plain C applications using X DevAPI and X DevAPI for C.
It also supports the legacy API of Connector/C++ 1.1 based on JDBC4.
To learn more about how to write applications using X DevAPI, see
“X DevAPI User Guide” at
…
The MySQL Development team is very happy to announce that MySQL 8.0.20 is now available for download at dev.mysql.com. In addition to bug fixes there are a few new features added in this release. Please download 8.0.20 from dev.mysql.com or from the MySQL Yum, APT, or SUSE repositories.…
Facebook Twitter LinkedIn
Dear MySQL users,
MySQL Connector/J 8.0.20 is the latest General Availability
release of
the MySQL Connector/J 8.0 series. It is suitable for use
with MySQL
Server versions 8.0, 5.7, and 5.6. It supports the Java
Database
Connectivity (JDBC) 4.2 API, and implements the X DevAPI.
This release includes the following new features and changes,
also
described in more detail on
https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-20.html
As always, we recommend that you check the “CHANGES” file in
the
download archive to be aware of changes in behavior that might
affect
your application.
To download MySQL Connector/J 8.0.20 GA, see the “General
Availability
(GA) Releases” tab at …
During this joint webinar our speakers, Alkin Tezuysal, Technical Expert at Percona and Sugu Sougoumarane, Co-Founder and CTO at PlanetScale, will provide attendees with hands-on experience using Vitess using Kubernetes. They will start by providing a quick overview of Vitess – including key concepts and terminology, and then describe the deployment options for both in Kubernetes.
The hands-on exercises will cover many of the key workflows with running a sharded system:
– Moving from an unsharded system to a vertical split one (moving
some tables to a different host)
– Sharding large tables across several instances
– Backups, Recoveries, and failovers (both planned and
unplanned).
Attendees are not expected to have any prior experience with Vitess but will find it useful if they have prior experience completing these tasks in a MySQL environment and general know-how …
[Read more]Queries per second (QPS) measures database throughput, but it does not reflect how hard MySQL is working. The latter is measured by Threads_running, expressed as a gauge (whereas QPS is a rate). Before discussing Threads_running, let’s consider an analogy:
Queries per second (QPS) measures database throughput, but it does not reflect how hard MySQL is working. The latter is measured by Threads_running, expressed as a gauge (whereas QPS is a rate). Before discussing Threads_running, let’s consider an analogy: