Oracle tries to reassure MySQL community with new features and transparency promises
#Infrastructure

Oracle tries to reassure MySQL community with new features and transparency promises

Privacy Reporter
3 min read

Oracle publishes blog post promising more transparency and new features for MySQL, including vector support, as community pushes for independent foundation to guide development

Oracle has published a blog post aimed at reassuring the MySQL community about its commitment to the open source database, promising new features including vector support and a more transparent development approach.

In a post co-authored by vice president Heather VanCura and MySQL community manager LenCasperova, Oracle declared that "MySQL is fundamental to our data strategy" and outlined plans to accelerate innovation in the database's core.

Oracle's promises to MySQL community

The company outlined several priorities for MySQL's development:

  • AI and cloud alignment, including vector support
  • Developer experience improvements
  • Performance enhancements like scaling and observability
  • Extensibility features
  • Ecosystem tooling and connector improvements

The blog post emphasized that new features would be prioritized based on "community selection principles," starting with low-risk capabilities that preserve stability and upgradeability. Oracle also committed to re-evaluating priorities in every release cycle.

Vector support gap

A significant concern driving community anxiety has been MySQL's lack of vector support. While PostgreSQL gained vector capabilities through pgvector v0.1.1 in April 2021, MySQL has lagged behind. Google already offers vector search for its Cloud SQL for MySQL service, and most commercial databases now provide some form of vector support.

Community push for independence

The blog post appears to be a response to growing pressure from the MySQL community. Last month, a group of influential users and developers invited Oracle to join plans to create an independent foundation to guide MySQL's development.

The group aims to establish a nonprofit to support the MySQL community and wants Oracle's cooperation as the owner of both the MySQL software and trademark.

Declining MySQL popularity

Community concerns stem partly from MySQL's declining market share. New projects and younger developers increasingly favor PostgreSQL, making it difficult to attract fresh talent to MySQL development. The community has criticized Oracle's management for lacking transparency, with development largely occurring behind closed doors through private code drops that offer "limited visibility into the roadmap or decision-making."

Additional concerns include missing features that should be standard in modern databases, particularly vector search capabilities needed for AI applications.

Recent turmoil

The push for change followed a January meeting in San Francisco that discussed recent job losses at Oracle's MySQL core development team. MySQL's founding developer Michael "Monty" Widenius expressed being "heartbroken" upon hearing the news. The meeting also highlighted a dramatic fall in the number of commits to the project, leading some to believe MySQL is reaching a critical crossroads.

Community response

According to sources, the community group is "positive on what was shared, but looking for more concrete information on timescales." More details are expected before the end of March.

The MySQL community's push for greater independence reflects broader tensions between corporate stewardship of open source projects and community-driven development models. As AI and vector capabilities become increasingly important for database workloads, MySQL's ability to compete with alternatives like PostgreSQL may depend on how quickly and transparently Oracle can deliver these features.

Featured image

The Register continues to monitor this developing story as the MySQL community awaits more concrete commitments from Oracle.

Comments

Loading comments...