New MySQL HeatWave capabilities released in 8.0.32 MySQL HeatWave has added new capabilities on both OCI and AWS platforms. Here is the list of features introduced in 8.0.32.   Query Performance Reduced HeatWave query compilation time for queries with large number of joins With the introduction of the multi-engine hypergraph-based optimizer with HeatWave in 8.0.31, […]

New MySQL HeatWave capabilities released in 8.0.32

MySQL Shell 8.0.32 was released last week and includes several bugfixes as well as some new features. Let's look into what was added in this new release. New Features $ cat ~/.my.cnf [client] user=root host=lefred password=lefreptwasswort $ mysqlsh MySQL Shell 8.0.32-commercial Copyright (c) 2016, 2023, Oracle and/or its affiliates. Oracle is a registered trademark of […]

Last year, in March 2022, our MySQL Operator for Kubernetes became Generally Available. Since then, several new features were added to our operator and along with the release of MySQL Server 8.0.32 comes a new release of our MySQL Operator for Kubernetes 8.0.32-2.0.8.  The goal of the MySQL Operator for Kubernetes is to provide an easy way […]

On January 17 2023, MySQL Server 8.0.32 was released. It is the latest release of our MySQL 8.0 General Availability Release. The new release introduces a few new features alongside with some deprecations, as well as bugfixes and security fixes. Let’s dive into some detail on these new features and changes MySQL Enterprise Optimizer mysql> […]

Announcing MySQL Server 8.0.32

In May 2020, I published a Planet for the MySQL Community Pluto Beta.  I was satisfied with the result and was considering it done, but I did not invest the time to promote it to release (a non-beta site was running for a few months without being advertised).  I finally came to it, and today I am happy to deprecate the beta and announce the release of Planet for the MySQL Community.&

A couple of days ago I was creating an index on the source and when I checked the replica side it was not replicated, so I just wanted to explain how the replication filter may increase the complexity of your DBA operations.

Replication occurs by reading events from the binary log of the source and then executing them on the replica. The events in the binary log are recorded in different formats, depending on the type of event. These formats are determined by the binary logging format used when the events were initially recorded on the source. The relationship between the binary logging formats and the terminology used during replication is as follows:

When using statement-based binary logging, the source writes SQL statements to the binary log. Replication of the source to the replica is performed by executing these SQL statements on the replica. This is known as statement-based replication (SBR), and it …

We had a couple of cases where clients reported that the MySQL error log was flooded with the below note:

2023-01-18T13:07:56.946323Z 2 [Note] InnoDB: Stopping purge
2023-01-18T13:07:56.948621Z 2 [Note] InnoDB: Resuming purge
2023-01-18T13:08:27.229703Z 2 [Note] InnoDB: Stopping purge
2023-01-18T13:08:27.231552Z 2 [Note] InnoDB: Resuming purge
2023-01-18T13:08:28.581674Z 2 [Note] InnoDB: Stopping purge

One of my colleagues Sami Ahlroos found that whenever we trigger a truncate on any table, the function is stopping the purge and then resuming it once it has found it stopped.

Below are the steps to reproduce.

1. Log verbosity needs to be set to 3 (the default value)

mysql> show variables like 'log_error_verbosity%';
+---------------------+-------+
| Variable_name       | Value |
+---------------------+-------+
| …

In this article, we are going to talk about the MySQL SUBSTRING() function with its variations. Here, you will find a detailed guide with the basic syntax and examples of how to use this function. Moreover, we will demonstrate the benefits of MySQL coding in a handy IDE - dbForge Studio for MySQL that can help you save a lot of time and energy.

The post Substring in MySQL – Syntax and Examples appeared first on Devart Blog.