Is Oracle’s Promise a New Era for MySQL? Community Reactions and Risks

Background

At a pre‑FOSDEM “MySQL and Friends” event in Belgium, Oracle’s roadmap for MySQL was discussed. Over the past five years the MySQL development team has been reduced and merged into Oracle’s cloud organization.

Oracle’s announced commitments

Oracle said it will migrate several features that were previously limited to the commercial edition into the community edition, with priority on developer‑facing capabilities. The most prominent announced feature is a set of vector functions (e.g., VECTOR_ADD, VECTOR_DOT) intended to accelerate AI and machine‑learning workloads by allowing column‑store style operations on high‑dimensional data.

Outstanding technical gaps

Despite the announced additions, MySQL still lacks a number of features that are already available in competing forks such as MariaDB or PostgreSQL. The most frequently cited gaps are:

Temporal tables (system‑versioned tables)

Dynamic columns

Sequences

Native UUID type

INET4/INET6 address types

Various syntax improvements introduced by MariaDB (e.g., CHECK constraints, enhanced window functions)

Community governance concerns

In early 2024 MySQL contributors met in San Francisco to discuss project governance. Percona co‑founder and MySQL performance expert Peter Zaitsev warned that Oracle is increasingly moving new functionality into its cloud and enterprise offerings without a clear open‑source delivery path, which could fragment the ecosystem.

“The current list is a set of promises with very few details on how they will work in practice,” Zaitsev said.

Implications for users

Developers evaluating MySQL must consider whether the promised community‑edition features will be delivered in a timely manner and whether the remaining gaps can be addressed through extensions or migration to alternative databases such as PostgreSQL or MariaDB.