Following the strong participation in our first Public MySQL Community Roadmap Discussion (with attendees joining from around the world), we are excited to invite you to the second edition of this public community webinar series.   In our latest blog post, we have published a brief recap of the first webinar—highlighting the key roadmap themes, how […]

Sensitive data has a way of showing up in unexpected places: an “email” column in a demo app, a forgotten “token” field in a logging table, or free-text notes that quietly become regulated data. I wanted a lightweight, repeatable way to answer a simple question on any MySQL instance: Where is sensitive data likely to […]

Oracle values the MySQL community. MySQL is fundamental to our data strategy. Oracle firmly believes that MySQL’s enduring strength arises from this vibrant global community. We are excited to work with the MySQL Community on the strategy we announced in Belgium, January 29, 2026, including adding more features and functionality, accelerating innovation directly in the […]

MySQL HeatWave AutoML is a native automated machine learning engine tightly integrated with the MySQL HeatWave database. It enables model training, inference, scoring, and explainability through SQL, executing directly on data in InnoDB tables or in external accessed via HeatWave Lakehouse from Object Storage. By operating in-database and in-memory on HeatWave nodes, AutoML eliminates data […]

I am continuing my blog post series on using indexes — or tables — as queues.  In this post, I cover Row Deletion Jobs (I do not call these purge jobs, to avoid confusion with the InnoDB Purge).  Such jobs are tempting to implement using an index, but this might be a wrong / suboptimal way.  I write about the right / better / cheaper way

In traditional MySQL, analytics require data to be ingested into InnoDB tables and processed on a single primary instance using row-based storage engine and limited parallelism. Scaling analytical workloads typically involves replicas, ETL pipelines, or even external analytics system.  With MySQL HeatWave, Oracle’s fully managed service in the cloud, analytics execution is offloaded to a […]

In traditional MySQL, analytics require data to be ingested into InnoDB tables and processed on a single primary instance using row-based storage engine and limited parallelism. Scaling analytical workloads typically involves replicas, ETL pipelines, or even external analytics system.  With MySQL HeatWave, Oracle’s fully managed service in the cloud, analytics execution is offloaded to a […]

As discussed in the earlier blog post A new Era of Community Engagement, there are many ways to connect with the MySQL Community.  MySQL Community: Ways to Learn, Connect, and Contribute (and See What’s Next)  MySQL is shaped by the people who use it—developers, DBAs, educators, user group leaders, and contributors around the world. The […]

I am starting a blog post series on using indexes — or tables — as queues.  I had this series in the back of my mind for some time.  This started a few years back when I worked on optimizing a row deletion job (I do not call this a purge job, to avoid confusion with the InnoDB Purge).  Such jobs can be generalized to using indexes (or tables) as queues (this is

This guide explains how to subtract days from dates across MySQL, H2, and other databases with different SQL dialects. Learn how to standardize behavior using compatibility modes, wrapper functions, and unified tooling so the same logic works reliably even when multiple database engines run side by side.

The post Mastering Cross-Database Date Manipulation: Subtracting Days in MySQL and H2  appeared first on Devart Blog.