[MySQL] Automatic schema change handling

[Rentacookie]

Currently, when syncing from a MySQL database database schema changes are ignored. This is problematic when those changes affect tables that are in the defined sync rules. The work around for that has been to redeploy the sync rules, thereby triggering a full re-sync.

This change set adds functionality to automatically handle schema changes affecting tables in the sync rules by listening for and parsing DDL query binlog events.

The basic mechanism for this works as follows:

1. Listen for query binlog events.
2. Parse these events to see if they affect the schema of tables in the sync rules.
3. Pause the binlog listener and update the stored bucket data based on the schema change if required
4. Restart the binlog listener.

Parsing of the query SQL is accomplished by using the node-sql-parser package. This does introduce a limitation in that if the library can't parse the query, we cannot easily interpret the intended schema change either. If this is the case, some best effort pattern matching is done to check if the query is a schema change that affects one of the replicated tables and a warning is logged.

The following schema changes are detectable:

• Create, rename, drop Table
• Truncate Table
• Create / Drop unique indexes and primary keys
• Add, modify, drop, rename columns

With the exception of Create Table, all of the schema events are detected by parsing the DDL statements received in the binlog query events. For Create table, these changes are picked up when row events are received for the new table.

[Copilot]

Pull Request Overview

Adds automatic handling of schema changes (DDL events) in MySQL replication and standardizes the use of a name property instead of table across sync-rules and storage modules.

• Renamed SourceTableInterface.table to .name everywhere in sync-rules and service-core
• Introduced BinLogListener logic to parse DDL statements and emit schema change events
• Updated all storage and API layers (Postgres, MySQL, MongoDB) to use table.name and qualifiedName

Reviewed Changes

Copilot reviewed 41 out of 42 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
packages/sync-rules/src/…/SourceTableInterface.ts	Renamed table → name in interface
packages/service-core/src/storage/SourceTable.ts	Refactored SourceTable to take an options object
modules/module-mysql/src/replication/zongji/BinLogListener.ts	Added DDL parsing, schema change handling, restart logic
modules/module-postgres-storage/src/storage/batch/PostgresBucketBatch.ts	Updated mapping to use table.name
modules/module-mysql/test/src/BinLogStream.test.ts	Fixed missing await and test descriptions
modules/module-mysql/src/utils/parser-utils.ts	Introduced DDL‐matching helper
packages/service-core/src/metrics/open-telemetry/util.ts	Added service.version and JSON import of package.json

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (4)

packages/service-core/src/metrics/open-telemetry/util.ts:66

• Use the semantic key 'service.name' (per OpenTelemetry conventions) instead of 'service' for the service identifier.

        ['service']: 'PowerSync',

modules/module-mysql/test/src/BinLogStream.test.ts:16

• [nitpick] Typo in the test suite title: it should read 'BinLogStream tests' to match the class name.

describe('BigLogStream tests', () => {

packages/service-core/src/storage/SourceTable.ts:55

• [nitpick] The hasReplicaIdentity getter was removed; verify that no downstream code relies on it or reintroduce it if still used.

   */

modules/module-postgres-storage/src/storage/batch/PostgresBucketBatch.ts:467

• Confirm that the table object has a name property; if it still uses table.table, update the mapping to use table.table or rename the source field accordingly.

        name: table.name,