MySQL Database Service is now easier to use and has flexible deployment options, including High Availability. While creating a new DB System using the web console, users can choose between Standalone, Highly Availability, and HeatWave deployments. The service will pre-populate the necessary fields with the recommended settings. You only need to provide the MySQL user name and password to get MySQL up and running.

With the Standalone option, users get a single-instance MySQL DB System back-ended by the resilient and secure OCI Block Volumes. This option is the most common for test and development environments.

The High Availability option enables applications to meet higher uptime requirements and zero data loss tolerance. When you select the High Availability option, a MySQL DB System with three instances is provisioned across different availability or fault domains. The data is replicated among the instances using a …

MySQL Database Service is now easier to use and has flexible deployment options, including High Availability. While creating a new DB System using the web console, users can choose between Standalone, Highly Availability, and HeatWave deployments. The service will pre-populate the necessary fields w...

Please find below the list of shows where you can find MySQL Community and/or the MySQL team at during April to June 2021:

• April 2021:

  • Data Love Conference/VIRTUAL, April 16, 2021

    • David Stokes, the MySQL Community Manager is going to talk about "Windowing Functions for Database Analytics", for the exact timing please check organizers' website.
  • MidwestPHP/VIRTUAL, April 22-23, 2021
    • David Stokes, the MySQL Community Manager is going to talk about "MySQL 8.0 New Features". The talk is scheduled for 1:50pm-2:30pm on April 22nd. 
    …

Please find below the list of shows where you can find MySQL Community and/or the MySQL team at during April to June 2021:

• April 2021:

  • Data Love Conference/VIRTUAL, April 16, 2021

    • David Stokes, the MySQL Community Manager is going to talk about "Windowing Functions for Database Analytics", for the exact timing please check organizers' website.
  • MidwestPHP/VIRTUAL, April 22-23, 2021
    • David Stokes, the MySQL Community Manager is going to talk about "MySQL 8.0 New Features". The talk is scheduled for 1:50pm-2:30pm on April 22nd. 
    …

Please find below the list of shows where you can find MySQL Community and/or the MySQL team at during April to June 2021: April 2021: Data Love Conference/VIRTUAL, April 16, 2021 David Stokes, the MySQL Community Manager is going to talk about "Windowing Functions for Database Analytics", for the e...

I recently published a blog post over on Medium about the differences in 2 versions of the MySQL COUNT() aggregate function: COUNT(*) and COUNT(column_name or expression). I wanted to share the post here with any readers who may be interested so continue reading for more on this post…

Image by anncapictures from Pixabay

Self-Promotion:

If you enjoy the content written here, by …

(based on a conversation with a colleague, and a bit of Twitter

)

A Conundrum

A developer colleague paged me with this:

mysql> select
UNIX_TIMESTAMP("2021-03-26 03:07:00" + INTERVAL 2 YEAR) -
UNIX_TIMESTAMP("2021-03-26 02:07:00" + INTERVAL 2 YEAR) as delta\G
delta: 420

It is obviously wrong, and weirdly so. It only works for “2 year”, not with other values:

mysql> select
UNIX_TIMESTAMP("2021-03-26 03:07:00" + INTERVAL 1-11 year_month) -
UNIX_TIMESTAMP("2021-03-26 02:07:00" + INTERVAL 1-11 year_month) as delta\G
delta: 3600

mysql> select
UNIX_TIMESTAMP("2021-03-26 03:07:00" + INTERVAL 1-12 year_month) -
UNIX_TIMESTAMP("2021-03-26 02:07:00" + INTERVAL 1-12 year_month) as delta\G
delta: 3600

mysql> select …

(based on a conversation with a colleague, and a bit of Twitter)

A Conundrum

A developer colleague paged me with this:

mysql> select
UNIX_TIMESTAMP("2021-03-26 03:07:00" + INTERVAL 2 YEAR) -
UNIX_TIMESTAMP("2021-03-26 02:07:00" + INTERVAL 2 YEAR) as delta\G
delta: 420

It is obviously wrong, and weirdly so. It only works for “2 year”, not with other values:

mysql> select
UNIX_TIMESTAMP("2021-03-26 03:07:00" + INTERVAL 1-11 year_month) -
UNIX_TIMESTAMP("2021-03-26 02:07:00" + INTERVAL 1-11 year_month) as delta\G
delta: 3600

mysql> select
UNIX_TIMESTAMP("2021-03-26 03:07:00" + INTERVAL 1-12 year_month) -
UNIX_TIMESTAMP("2021-03-26 02:07:00" + INTERVAL 1-12 year_month) as delta\G
delta: 3600

mysql> select
UNIX_TIMESTAMP("2021-03-26 03:07:00" + INTERVAL 1-13 year_month) -
UNIX_TIMESTAMP("2021-03-26 …

MySQL installation security is something that should be on the  mind of every MySQL DBA. While we have discussed how you should take care of your MySQL security as a whole (take a look at some of our previous posts, specifically the MySQL security series Part One and Part Two), we haven’t  discussed specific security-related issues, including  those issues related to privileges. We do that here.

What are Privileges in MySQL?

Privileges in MySQL can be granted to accounts. If you grant account privileges in MySQL, you determine which operations the account can perform. Privileges can be granted to either databases or database objects (tables, indexes, views etc.) Privileges can also be dynamic or static. Static privileges …

Over the decades we have been reading the MySQL error log from the server system file, if there are any issues in MySQL or any unknown restart happened , generally we look at the mysql error log.

By default MySQL error log can be found in the default path /var/log/mysqld.log , or it can be explicitly configured using the variable log_error.

Few drawbacks using MySQL error log as FILE

• Possibility of missing genuine errors while reading lengthy information.
• Filtering of errors for the particular date and timeframes.
• Cannot provide the DB server access to developers because of fear of mishandling DB servers.

To overcome the above issues , from MySQL …