GPL-3.0 OPEN SOURCE

openHalo: open-source MySQL compatibility for PostgreSQL.

openHalo is a Halo Tech-initiated GPL-3.0 project that helps PostgreSQL work with applications using commonly used MySQL dialects, semantics, and the MySQL communication protocol—so migration can require fewer code changes, subject to workload validation.

Why openHalo exists

PostgreSQL and MySQL have different communication protocols, dialects, semantics, catalogs, and ecosystem expectations. Applications written for MySQL can therefore require more than a data copy before they can work with PostgreSQL.

openHalo develops that compatibility path in public. Its goal is to let developers inspect the implementation, build it from source, test familiar application workflows, document gaps, and improve the project through reproducible contributions.

Compatibility at the surfaces applications use

The repository describes support for commonly used MySQL dialects, semantics, and communication protocol. That wording defines the project direction; it is not a promise of complete compatibility.

MySQL communication protocol

Expose a connection path for MySQL-facing clients and application stacks.

Common SQL and semantics

Interpret commonly used MySQL syntax and behavior on a PostgreSQL-based system.

Clients and drivers

Let teams test familiar MySQL command-line clients, connectors, drivers, frameworks, and development workflows.

Fewer migration changes

Reduce the code that may need to change for MySQL 5.7-and-later applications, while keeping workload-specific gaps visible.

How to inspect and build the project

openHalo starts from PostgreSQL and adds compatibility work where MySQL-facing applications meet the database: connection protocol, parsing, SQL semantics, and related behavior. The public repository is the canonical place to inspect what is implemented and what remains under development.

The Quick Tutorial is a source-build path. Its broad-listen and host-access examples are suitable only as development or test starting points; production security, network exposure, authentication, and operating policy require separate review.

Core project capabilities

Protocol-facing access

A MySQL communication path for compatible clients and drivers.

Dialect interpretation

Implementation work around commonly used MySQL statements, types, functions, and behavior.

PostgreSQL foundation

A PostgreSQL-based core that remains inspectable through the public source tree.

Source-first validation

Build instructions, tests, issue history, and discussions let contributors verify exact behavior instead of relying on a blanket compatibility percentage.

Teaching practice and community participation

Halo Tech’s official project page reports that openHalo has been used as a graduate teaching-practice project at Peking University. The teaching path gives students a real database codebase through which to study systems engineering and contribute practical improvements.

Participation is broader than code. Reproducible tests, documentation corrections, examples, compatibility reports, design discussion, and careful issue triage all help make the project easier to evaluate and maintain.

Choose a contribution path

Code

Build the source, run relevant checks, and submit focused pull requests.

Documentation

Clarify build steps, behavior, examples, or limitations that you can reproduce.

Issues

Browse the current issue record and add useful context where contribution permissions allow.

Discussion

Use GitHub Discussions for project questions and design conversation.

Explore the code—or take the commercial product path.

Use the public repositories for openHalo. For a licensed Halo Database package and evaluation license, coordinate directly with Halo Tech.