epic: MySQL support

[wwoytenko]

MySQL support epic. Here we log state of development process.

Beta versions

• Greenmask v1.0.0b1

UPD (2025-12-19):

A "short" list of TODOs for the first pre-release:

• Port CMD transformer Feat/gm v1 port cmd transformer #359
• Introduce column class. For example class.Textual represents all TEXT-like column types feat: Implemented TypeClass #360
• Implement list-dumps command feat: Ported list-dumps command #361
• Implement validate command feat: Implement validate command for MySQL and GM V1 #363
• Implement list-transformers command feat/gm v1 transformers command #365
• Playground for MySQL feat: MySQL docker playground and fixes #367
• Implement show-dump command
• Implement show-transformer command feat/gm v1 transformers command #365
• Implement delete command feat: impl delete command #364
• Write unit tests for MySQL driver using a real MySQL8 test container Feat/gm v1 mysql driver real tests #366
• Write a bunch of integration tests feat: Introduce v1 integration test suite #375
• Implement transformer inharitance (references + partitioned tables)
• Revise documentation and add info about MySQL engine
• Create build for mysql (v1) (docker and binaries) - for 8.4 and 8.0 versions Add build steps for V1 version #374

[wwoytenko]

This is still a work in progress. We are currently somewhere in the middle, and I believe the beta version will be ready by the end of Q1 2025. This also requires significant changes to the existing codebase, as we need to refactor the current framework to support additional DBMS in the future.

Thank you all for your patience—we’ll keep you updated!

[wwoytenko]

Hey everyone,

The work turned out to be more complex than we thought, so we’ve had some delays. Here's a quick update.

Why the delay:

We're building a platform at the same time, so instead of just adding MySQL support, we're making sure it works inside the platform too. This means a lot of code refactoring, adding new features, optimizing, and doing integration tests.

We want to release Greenmask v1.0.0 with solid MySQL support — stable, minimal bugs, ready to use.

We also took this chance to clean up and improve the PostgreSQL code.

What’s done so far:

• Refactored the codebase
• Basic transformations are working with the MySQL engine
• We're now working on adding the Subset system for MySQL
• MySQL 8 is supported (we might add other versions later — feel free to request!)

Still in progress:

• Integrating the MySQL driver
• More integration tests + bug fixes
• Figuring out the best format to store table data (currently using SQL insert statements, but might switch to CSV or JSON-like later)
• Adding mysqldump support

We’re aiming to release the first version by end of May 2025, but that could change depending on how things go.

We’re working on 3 areas at once — MySQL support, platform development, and current version maintenance — so we’re happy to have contributors help out! Especially if you’re into:

• MySQL
• Golang
• Frontend work

Reach out if you’re interested. Thanks for being patient with us!

[wwoytenko]

This feature is still a work in progress, but we’ve made significant headway. We aim to publish a pre-release between June 15 and June 30. However, we won’t meet that deadline exactly. Instead, we will push the current results from our private repository and continue development publicly. Stay tuned to Greenmask.

[wwoytenko]

We've just pablished a huge increment in the #310 MR related to the Greenmask v1.0.0 and MySQL. We are still on it, but since now we are going to publish small code increments and make a process clear and transparent. Do not hasitate to reach us out if you have any MySQL related ideas to do. Thanks.

[wwoytenko]

Good news here!!!

I was able to run greenmask dump in MySQL in #312.

Status report:

Completed:

• Chosen dump/restore format: CSV + LOAD DATA [LOCAL] INFILE. This may change later, but we believe it's the best option for now.
• Almost fully implemented the new Greenmask v1 framework.
• Implemented the greenmask dump command for MySQL.
• Revised original go std CSV Reader/Writer - now it works with []byte instead of string

WIP:

• Porting transformers to the new framework (only Replace is migrated so far).
• Testing the transformation pipeline for MySQL.
• Implementing the validate and restore commands.
• Setting up integration testing with MySQL 8 (will be the first supported DB).
• Preparing CI/CD pipelines for MySQL builds.
• Cover with unit testes
• Verifying how DBMSDriver behaves with new or unregistered column types.
• Performance and stability tests