MySQL 9.7.0 brings JSON duality view writes to Community Server

MySQL’s April 21 release notes for version 9.7.0 expand JSON duality views in Community Server to support inserts, updates and deletes. Previously, the Community edition’s support was limited to DDL operations, according to the official notes.

Document writes meet relational structure

The same release adds support for auto-increment columns in duality-view DML. It also treats qualifying UNIQUE NOT NULL keys as primary-key equivalents for CREATE and ALTER statements.

For teams exposing relational records through a document interface, our analysis is that write support changes the evaluation from presentation to ownership. The important question becomes how a document update maps to the application’s existing constraints, generated identifiers and transaction boundaries.

A useful prototype should start with a real aggregate containing more than one related record. Exercise insertion with generated keys, a partial business update and a rejected update. Check the base tables after each operation, not just the returned document.

Keep edition boundaries in the upgrade plan

The notes also introduce dynamic data masking policies specifically for Enterprise Edition. That availability should not be inferred from the Community duality-view announcement.

Before planning a migration, separate features available in the deployed edition from features merely described on the same release page. Record the exact server build and schema definition with each test result.

The practical next step is a round-trip fixture: create through the document-facing interface, read through the existing relational path, update in the opposite direction and verify the resulting document. That gives application owners a concrete basis for deciding whether duality views simplify their particular boundary.