@vlasky/zongji 0.5.8 → 0.6.0

package/.tap/test-results/test_await_end.js.tap

@@ -0,0 +1,19 @@
+Test file starting
+TAP version 14
+Invalid host test starting
+Got error: ENOTFOUND
+# Subtest: Connect to an invalid host
+    ok 1 - should be equal
+Invalid host test ending
+    1..1
+ok 1 - Connect to an invalid host # time=112.602ms
+
+MySQL test starting
+Query callback! err: null
+# Subtest: Simple MySQL query
+    ok 1 - query worked
+MySQL test ending
+    1..1
+ok 2 - Simple MySQL query # time=11.899ms
+
+1..2

package/.tap/test-results/test_await_end2.js.tap

@@ -0,0 +1,27 @@
+TAP version 14
+# Subtest: Connect to an invalid host
+    ok 1 - should be equal
+    1..1
+ok 1 - Connect to an invalid host # time=11.133ms
+
+# Subtest: Simple MySQL query
+    not ok 1 - test unfinished
+      ---
+      at:
+        fileName: test_await_end2.js
+        lineNumber: 35
+        columnNumber: 5
+        isToplevel: true
+      stack: |
+        test_await_end2.js:35:5
+      test: Simple MySQL query
+      source: |
+        });
+      
+        tap.test('Simple MySQL query', async test => {
+        ----^
+          const conn = mysql.createConnection(settings);
+      ...
+    
+    Bail out! test unfinished
+Bail out! test unfinished

package/.tap/test-results/test_debug_init.js.tap

@@ -0,0 +1,23 @@
+Test file starting
+TAP version 14
+Invalid host test starting
+Got error: ENOTFOUND
+# Subtest: Connect to an invalid host
+    ok 1 - should be equal
+    1..1
+Teardown called
+ok 1 - Connect to an invalid host # time=10.054ms
+
+MySQL connection test starting
+Connection object created
+Running query...
+Query issued, waiting for callback...
+Query callback received
+Query result: [ { test: 1 } ]
+Connection destroyed
+# Subtest: Create MySQL connection
+    ok 1 - connection worked
+    1..1
+ok 2 - Create MySQL connection # time=11.332ms
+
+1..2

package/.tap/test-results/test_debug_init2.js.tap

@@ -0,0 +1,35 @@
+Test file starting
+TAP version 14
+Invalid host test starting
+Got error: ENOTFOUND
+# Subtest: Connect to an invalid host
+    ok 1 - should be equal
+    1..1
+Teardown called
+ok 1 - Connect to an invalid host # time=9.46ms
+
+Init db test starting
+Creating connection...
+Connection created, running querySequence...
+querySequence called, waiting for callback...
+# Subtest: Init db with querySequence
+    not ok 1 - test unfinished
+      ---
+      at:
+        fileName: test_debug_init2.js
+        lineNumber: 37
+        columnNumber: 5
+        isToplevel: true
+      stack: |
+        test_debug_init2.js:37:5
+      test: Init db with querySequence
+      source: |
+        });
+      
+        tap.test('Init db with querySequence', async test => {
+        ----^
+          console.log('Init db test starting');
+      ...
+    
+    Bail out! test unfinished
+Bail out! test unfinished

package/.tap/test-results/test_invalid_host.js.tap

@@ -0,0 +1,34 @@
+Test file starting at: 1769661151919
+TAP version 14
+Invalid host test starting at: 1769661151922
+ZongJi.start() called at: 1769661151927
+Got error at: 1769661151930 ENOTFOUND
+# Subtest: Connect to an invalid host
+    ok 1 - should be equal
+    1..1
+Teardown called at: 1769661151931
+ok 1 - Connect to an invalid host # time=10.183ms
+
+Init db test starting at: 1769661151932
+# Subtest: Initialise testing db
+    not ok 1 - test unfinished
+      ---
+      at:
+        fileName: test_invalid_host.js
+        lineNumber: 30
+        columnNumber: 5
+        isToplevel: true
+      stack: |
+        test_invalid_host.js:30:5
+      test: Initialise testing db
+      source: |
+        });
+      
+        tap.test('Initialise testing db', async test => {
+        ----^
+          console.log('Init db test starting at:', Date.now());
+          try {
+      ...
+    
+    Bail out! test unfinished
+Bail out! test unfinished

package/.tap/test-results/test_minimal.js.tap

@@ -0,0 +1,26 @@
+Test file starting
+TAP version 14
+Invalid host test starting
+Calling zongji.start()
+zongji.start() returned
+Got error: ENOTFOUND
+# Subtest: Connect to an invalid host
+    ok 1 - should be equal
+Calling test.end()
+    1..1
+Teardown starting
+Teardown completed
+ok 1 - Connect to an invalid host # time=10.599ms
+
+MySQL test starting
+Calling conn.query()
+conn.query() returned, waiting...
+test.end() returned
+Query callback! err: null
+# Subtest: Simple MySQL query
+    ok 1 - query worked
+Timeout reached
+    1..1
+ok 2 - Simple MySQL query # time=5001.569ms
+
+1..2

package/.tap/test-results/test_queryseq.js.tap

@@ -0,0 +1,14 @@
+Test file starting
+TAP version 14
+Init db test starting
+Creating connection...
+Connection created, running querySequence...
+querySequence called, waiting for callback...
+querySequence callback received, error: null
+Init complete
+# Subtest: Init db with querySequence
+    ok 1 - init worked
+    1..1
+ok 1 - Init db with querySequence # time=18.904ms
+
+1..1

package/.tap/test-results/test_timing.js.tap

@@ -0,0 +1,17 @@
+Test file starting at: 1769661140028
+TAP version 14
+Test 1 starting at: 1769661140031
+Test 1 ending at: 1769661140132
+# Subtest: Test 1
+    ok 1 - test 1 done
+    1..1
+ok 1 - Test 1 # time=103.078ms
+
+Test 2 starting at: 1769661140135
+Test 2 init complete at: 1769661140170
+# Subtest: Test 2 - init db
+    ok 1 - database initialized
+    1..1
+ok 2 - Test 2 - init db # time=35.205ms
+
+1..2

package/.tap/test-results/test_unref.js.tap

@@ -0,0 +1,15 @@
+TAP version 14
+# Subtest: Connect to an invalid host - with explicit cleanup
+    ok 1 - should be equal
+    not ok 2 - getaddrinfo ENOTFOUND wronghost
+      ---
+      errno: -3008
+      code: ENOTFOUND
+      syscall: getaddrinfo
+      hostname: wronghost
+      fatal: true
+      tapCaught: unhandledRejection
+      ...
+    
+    Bail out! getaddrinfo ENOTFOUND wronghost
+Bail out! getaddrinfo ENOTFOUND wronghost

package/CHANGELOG.md

@@ -0,0 +1,55 @@
+# Changelog
+
+All notable changes to @vlasky/zongji since forking from nevill/zongji.
+
+## [0.6.0] - 2026-02-13
+
+- Migrate from @vlasky/mysql to mysql2
+- Convert codebase to ES modules
+- Add TypeScript definitions
+- Add official support for MySQL 8.4
+- Fix sequence ID warnings when using compression with binlog streams
+- Fix connection cleanup in stop() to prevent reuse of destroyed connections
+- Add stopped flag to support dynamic filter updates and safe stop during init
+- Fix flaky error test by handling all error events instead of just the first
+
+## [0.5.9] - 2023-01-11
+
+- Allow BLOB columns with utf8mb3 charset
+
+## [0.5.8] - 2021-09-19
+
+- Internal version bump
+
+## [0.5.7] - 2021-07-08
+
+- Fix connection when binlog_checksum is NONE
+
+## [0.5.6] - 2021-04-30
+
+- Update to @vlasky/mysql 2.18.5 with keepalive probe packet support
+
+## [0.5.5] - 2021-04-17
+
+- Update to @vlasky/mysql 2.18.4 to support additional charset collations in MySQL 8
+
+## [0.5.4] - 2021-04-17
+
+- Update to @vlasky/mysql 2.18.3 to support caching_sha2_password authentication plugin (MySQL 8 default)
+
+## [0.5.3] - 2021-03-24
+
+- Update to @vlasky/mysql 2.18.2 to support new MySQL 8 error codes
+- Handle table map events that change table IDs (from YousefED)
+- Fix null value in JSON column causing buffer RangeError (from YousefED)
+- MySQL 8 compatibility fix for column mapping query order
+
+## [0.5.2] - 2020-11-11
+
+- Fix IEEE754 conversion error using DataView (from jefbarn)
+- Update dependencies
+
+## [0.5.1] - 2019-11-09
+
+- Initial fork from nevill/zongji
+- Add binlog_row_image support

package/CLAUDE.md

@@ -0,0 +1,99 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+@vlasky/zongji is a MySQL binlog listener for Node.js that supports MySQL 5.7-8.4. It provides real-time change data capture (CDC) by listening to MySQL binary log events.
+
+The library uses `mysql2` for connections and authentication while implementing custom binlog protocol parsing.
+
+## Development Commands
+
+```bash
+# Install dependencies
+npm install
+
+# Run zongji tests (requires Docker)
+npm test
+
+# Run linter
+npm run lint
+
+# Check TypeScript definitions and JS type errors
+npm run checkjs
+```
+
+## Docker MySQL Client Command
+
+- Use this command to launch the mysql client:  docker exec -it docker-mysql mysql -u root -psecret
+
+## Architecture Overview
+
+The codebase follows an event-driven architecture with these key components:
+
+1. **Main Entry**: `index.js` - ZongJi class extending EventEmitter
+2. **Dual Connection Pattern**:
+   - Control connection for queries/metadata
+   - Binlog connection for streaming events
+3. **Event Processing Pipeline**:
+   - Custom `Command` class in `lib/sequence/binlog.js` for mysql2 integration
+   - Binary protocol parsing via `Parser` class in `lib/reader.js`
+   - Event type definitions in `lib/binlog_event.js`
+   - Row event handling in `lib/rows_event.js`
+   - Type-specific decoders (datetime, JSON) in lib/
+
+## Key Implementation Details
+
+- **Module System**: Uses ES modules (ESM) with import/export syntax
+- **TypeScript Support**: Includes TypeScript definitions (index.d.ts)
+- **MySQL Driver**: Uses `mysql2` for connections, authentication (including caching_sha2_password), and base protocol
+- **Custom Binlog Command**: Implements COM_BINLOG_DUMP (0x12) via custom `Command` class compatible with mysql2's command queue
+- **Parser Compatibility**: Custom `Parser` class in `lib/reader.js` provides mysql2 packet parsing interface
+- **Event Filtering**: Schema and event-type filtering before emission
+- **Position Tracking**: Maintains binlog filename and position for resumable processing
+- **Table Metadata**: Caches table structures for efficient row decoding
+- **Checksum Support**: Automatic detection and handling of binlog checksums (CRC32)
+- **Timezone Support**: Datetime decoders respect mysql2's `timezone` connection option
+- **GTID Support**: Parses Gtid, AnonymousGtid, and PreviousGtids events
+
+## Testing
+
+Tests use Docker Compose with MySQL containers:
+- Configuration in `docker-compose.yml`
+- Test database setup in `test/helpers/`
+- Event-specific tests in `test/` directory
+- Uses `tap` test framework (v21+)
+
+**Before running tests**, always:
+1. Ensure Docker containers are running: `docker-compose up -d` (or specific services e.g. `docker-compose up -d mysql80 mysql84`)
+2. Note: MySQL 5.7 image does not support ARM64 (Apple Silicon) — skip it on those machines
+3. Wait for MySQL to be ready before running tests (containers need ~10-15 seconds to initialise)
+
+When modifying binlog parsing or adding event support, ensure tests cover:
+- Event parsing correctness
+- Position tracking accuracy
+- Error handling scenarios
+- MySQL version compatibility
+
+## Common Development Tasks
+
+1. **Adding new event types**: Update `lib/binlog_event.js` and `lib/code_map.js`
+2. **Supporting new MySQL types**: Modify type parsing in `lib/rows_event.js` and `lib/common.js`
+3. **Protocol changes**: Update `lib/sequence/binlog.js` for command handling, `lib/reader.js` for parsing
+4. **Connection handling**: Modify `index.js` for connection lifecycle changes
+
+## Requirements
+
+- Node.js >= 18.0
+- MySQL 5.7, 8.0, or 8.4 with binlog enabled
+
+## Development Principles
+
+- **Avoid Duplicate Code**: Avoid creating duplicate code or duplicate functionality
+
+# important-instruction-reminders
+Do what has been asked; nothing more, nothing less.
+NEVER create files unless they're absolutely necessary for achieving your goal.
+ALWAYS prefer editing an existing file to creating a new one.
+NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested by the User.

package/GTID.md

@@ -0,0 +1,54 @@
+# GTID discussion
+
+This file summarizes our discussion about GTID handling in zongji and possible
+exposure patterns for application use.
+
+## Current behavior
+
+- GTID-related binlog events are parsed and emitted as their own events:
+  - `Gtid`
+  - `AnonymousGtid`
+  - `PreviousGtids`
+- The GTID event objects contain:
+  - `event.gtid` (string: `uuid:sequence`)
+  - `event.sid` (UUID string)
+  - `event.gno` (sequence number)
+  - For `PreviousGtids`: `event.sids` and `event.gtidSet`
+- Row events (`WriteRows`, `UpdateRows`, `DeleteRows`) do not currently include
+  GTID information.
+
+## Practical uses for GTID
+
+- Checkpointing: store the latest GTID and resume from it after restart/failover.
+- Deduplication / exactly-once: use GTID as a unique transaction ID.
+- Auditing / debugging: correlate binlog events with replication state.
+
+## Transaction boundaries
+
+- Start of a GTID transaction:
+  - `Gtid` event (when `gtid_mode=ON`).
+- Start of a non-GTID transaction:
+  - `Query` event with `BEGIN`.
+- End (commit) of row-based transactions:
+  - `Xid` event.
+- End (commit/rollback) of statement-based transactions:
+  - `Query` event with `COMMIT` or `ROLLBACK`.
+
+## Open questions / options
+
+1) Add `zongji.lastGtid`:
+   - Updated when a `Gtid` or `AnonymousGtid` event is received.
+   - Useful for external checkpointing without subscribing to GTID events.
+
+2) Attach `event.gtid` to row events:
+   - Copied from `zongji.lastGtid`.
+   - Lets users compare row events to see when GTID changes.
+   - Only reliable when `gtid_mode=ON` (undefined for non-GTID transactions).
+
+3) Add high-level transaction boundary events:
+   - Emit `transactionStart`/`transactionCommit`/`transactionRollback` with
+     GTID and event metadata.
+
+Notes:
+- Adding `event.gtid` and/or `zongji.lastGtid` is additive and should be
+  backward-compatible, but it depends on GTID mode being enabled in MySQL.

package/README.md

@@ -1,23 +1,21 @@
-A MySQL 8.0-compatible fork of ZongJi - a MySQL binlog listener for Node.js, [originally created by Nevill Dutt](https://github.com/nevill/zongji).
+MySQL binlog-based change data capture (CDC) for Node.js, [originally created by Nevill Dutt](https://github.com/nevill/zongji).
 
-[@vlasky/zongji](https://github.com/vlasky/zongji) has been tested working with MySQL 5.5, 5.6, 5.7 and 8.0.
+[@vlasky/zongji](https://github.com/vlasky/zongji) has been tested working with MySQL 5.7, 8.0 and 8.4.
 
-It leverages [`@vlasky/mysql`](https://github.com/vlasky/mysql), a fork of [`mysql`](https://github.com/mysqljs/mysql) with the following enhancements:
-
-* Support for authentication using the caching_sha2_password plugin, the new default authentication method in MySQL 8.0
-* Partial support for the MySQL compressed protocol (reads compressed data sent by server)
-* Optional sending of keepalive probe packets to check the state of the connection to the MySQL server and help keep the connection open when the network socket is idle
+It leverages [`mysql2`](https://github.com/sidorares/node-mysql2) for connections and authentication, while using zongji's binlog parsing and event pipeline.
 
 # Latest Release
 
-ZongJi release versions since 0.5.0 only support Node.js version 8 and above.
+Version 0.6.0 is a major modernisation that rewrites the codebase to use the mysql2 module, ES6 syntax and ESM exports, adds TypeScript definitions, and adds official support for MySQL 8.4.
 
-Version 0.4.7 is the last release that supports Node.js version 4.x.
+Version 0.5.9 is the last release that supports Node.js versions below 18 and CommonJS.
 
 ## Quick Start
 
 ```javascript
-let zongji = new ZongJi({ /* ... MySQL Connection Settings ... */ });
+import ZongJi from '@vlasky/zongji';
+
+const zongji = new ZongJi({ /* ... MySQL Connection Settings ... */ });
 
 // Each change to the replication log results in an event
 zongji.on('binlog', function(evt) {
@@ -30,18 +28,37 @@ zongji.start({
 });
 ```
 
+### GTID example
+
+```javascript
+zongji.on('binlog', function(evt) {
+  const type = evt.getTypeName();
+  if (type === 'Gtid' || type === 'AnonymousGtid') {
+    console.log('GTID:', evt.gtid, 'SID:', evt.sid, 'GNO:', evt.gno);
+  }
+});
+```
+
+### TypeScript
+
+TypeScript definitions are included:
+
+```typescript
+import ZongJi from '@vlasky/zongji';
+```
+
 For a complete implementation see [`example.js`](example.js)...
 
 ## Installation
 
-* Requires Node.js v8+
+* Requires Node.js v18+
 
   ```bash
   $ npm install @vlasky/zongji
   ```
 
 * Enable MySQL binlog in `my.cnf`, restart MySQL server after making the changes.
-  > From [MySQL 5.6](https://dev.mysql.com/doc/refman/5.6/en/replication-options-binary-log.html), binlog checksum is enabled by default. Zongji can work with it, but it doesn't really verify it.
+  > Binlog checksum is enabled by default in all supported MySQL versions. Zongji can work with it, but it doesn't verify the checksum.
 
   ```
   # Must be unique integer from 1-2^32
@@ -66,12 +83,12 @@ For a complete implementation see [`example.js`](example.js)...
 
 The `ZongJi` constructor accepts one argument of either:
 
-* An object containing MySQL connection details in the same format as used by [package mysql](https://npm.im/mysql)
-* Or, a [mysql](https://npm.im/mysql) `Connection` or `Pool` object that will be used for querying column information.
+* An object containing MySQL connection details in the same format as used by [package mysql2](https://npm.im/mysql2)
+* Or, a [mysql2](https://npm.im/mysql2) `Connection` or `Pool` object that will be used for querying column information.
 
 If a `Connection` or `Pool` object is passed to the constructor, it will not be destroyed/ended by Zongji's `stop()` method.
 
-If there is a `dateStrings` `mysql` configuration option in the connection details or connection, `ZongJi` will follow it.
+The `dateStrings` and `timezone` configuration options from the connection details are respected for date/time value handling.
 
 Each instance includes the following methods:
 
@@ -85,7 +102,7 @@ Some events can be emitted in different phases:
 
 Event Name | Description
 -----------|------------------------
-`ready`    | This event is occurred right after ZongJi successfully established a connection, setup slave status, and set binlog position.
+`ready`    | This event occurs right after ZongJi successfully establishes a connection, sets up replica (slave) status, and sets the binlog position.
 `binlog`   | Once a binlog is received and passes the filter, it will bubble up with this event.
 `error`    | Every error will be caught by this event.
 `stopped`  | Emitted when ZongJi connection is stopped (ZongJi#stop is called).
@@ -116,6 +133,9 @@ Event name  | Description
 `rotate`    | [New Binlog file](https://dev.mysql.com/doc/internals/en/rotate-event.html) Not required to be included to rotate to new files, but it is required to be included in order to keep the `filename` and `position` properties updated with current values for [graceful restarting on errors](https://gist.github.com/numtel/5b37b2a7f47b380c1a099596c6f3db2f).
 `format`    | [Format Description](https://dev.mysql.com/doc/internals/en/format-description-event.html)
 `xid`       | [Transaction ID](https://dev.mysql.com/doc/internals/en/xid-event.html)
+`gtid`      | GTID event with `gtid`, `sid`, `gno` properties
+`anonymousgtid` | Anonymous GTID event (same shape as `gtid`)
+`previousgtids` | Previous GTIDs event with `gtidSet` and `sids`
 `tablemap`  | Before any row event (must be included for any other row events)
 `writerows` | Rows inserted, row data array available as `rows` property on event object
 `updaterows` | Rows changed, row data array available as `rows` property on event object
@@ -132,20 +152,23 @@ Name   | Description
 
 ## Important Notes
 
-* :star2: [All types allowed by `mysql`](https://github.com/mysqljs/mysql#type-casting) are supported by this package.
+* :star2: All MySQL column types are supported, with type casting similar to [mysql2](https://github.com/sidorares/node-mysql2).
 * :speak_no_evil: 64-bit integer is supported via package big-integer(see #108). If an integer is within the safe range of JS number (-2^53, 2^53), a Number object will returned, otherwise, will return as String.
 * :point_right: `TRUNCATE` statement does not cause corresponding `DeleteRows` event. Use unqualified `DELETE FROM` for same effect.
-* When using fractional seconds with `DATETIME` and `TIMESTAMP` data types in MySQL > 5.6.4, only millisecond precision is available due to the limit of Javascript's `Date` object.
+* When using fractional seconds with `DATETIME` and `TIMESTAMP` data types, only millisecond precision is available due to the limit of Javascript's `Date` object.
+* Binlog checksums (e.g. `CRC32`) are supported; zongji will detect and ignore the checksum bytes at the end of row events.
 
 ## Run Tests
 
-* install [Docker](https://www.docker.com/community-edition#download)
-* run `docker-compose up` and then `./docker-test.sh`
+* Install [Docker](https://www.docker.com/community-edition#download)
+* Run `docker-compose up -d` to start MySQL containers
+* Run `npm test` to execute the test suite
 
 ## References
 
 The following resources provided valuable information that greatly assisted in creating ZongJi:
 
+* https://github.com/sidorares/node-mysql2
 * https://github.com/mysqljs/mysql
 * https://github.com/felixge/faster-than-c/
 * https://web.archive.org/web/20130117004733/https://intuitive-search.blogspot.co.uk/2011/07/binary-log-api-and-replication-listener.html
@@ -153,7 +176,7 @@ The following resources provided valuable information that greatly assisted in c
 * https://kkaefer.com/node-cpp-modules/
 * https://dev.mysql.com/doc/internals/en/replication-protocol.html
 * https://web.archive.org/web/20200201195450/https://www.cs.wichita.edu/~chang/lecture/cs742/program/how-mysql-c-api.html
-* https://github.com/jeremycole/mysql_binlog (Ruby implemenation of MySQL binlog parser)
+* https://github.com/jeremycole/mysql_binlog (Ruby implementation of MySQL binlog parser)
 * https://dev.mysql.com/doc/internals/en/date-and-time-data-type-representation.html
 
 ## License

package/TODO.md

@@ -0,0 +1,43 @@
+# TODO: MySQL 8 binlog events and partial JSON support
+
+This note summarizes the discussion about additional MySQL 8 binlog events and
+partial JSON handling.
+
+## Events not currently supported
+
+- PARTIAL_UPDATE_ROWS_EVENT
+- TRANSACTION_PAYLOAD_EVENT
+- HEARTBEAT_LOG_EVENT_V2
+
+Currently these events are not mapped in `lib/code_map.js`, so they arrive as
+`Unknown` and are effectively ignored.
+
+## Practical impact
+
+- PARTIAL_UPDATE_ROWS_EVENT:
+  - Emitted when `binlog_row_value_options=PARTIAL_JSON`.
+  - Encodes JSON diffs instead of full JSON values.
+  - Only appears if partial JSON is enabled.
+- TRANSACTION_PAYLOAD_EVENT:
+  - Used with transaction compression (MySQL 8.0.20+).
+  - Wraps multiple events in a compressed payload.
+  - Only appears if transaction compression is enabled.
+- HEARTBEAT_LOG_EVENT_V2:
+  - Replication keepalive/monitoring; no data changes.
+
+## Possible support approach
+
+1) Add event mappings and parsers:
+   - Update `lib/code_map.js` to map event IDs.
+   - Implement parser classes in `lib/binlog_event.js` (and any helpers).
+2) Extend tests:
+   - Add targeted tests that enable the corresponding MySQL settings.
+   - Assert event emission and basic payload shape.
+
+## Partial JSON strategy options
+
+- Option A: expose raw JSON diff data from PARTIAL_UPDATE_ROWS_EVENT.
+  - Lowest effort; consumers apply patches.
+- Option B: reconstruct full JSON values.
+  - Requires FULL row image or a row-state cache to apply diffs.
+  - More complex but produces complete row values.

package/docker-compose.yml

@@ -1,32 +1,33 @@
 ---
-version: '2'
 services:
-  mysql55:
-    image: mysql:5.5
+  mysql57:
+    image: mysql:5.7
     command: [ "--server-id=1", "--log-bin=/var/lib/mysql/mysql-bin.log", "--binlog-format=row"]
     networks:
       default:
         aliases:
-          - mysql55
+          - mysql57
     environment:
-      MYSQL_ROOT_PASSWORD: numtel
+      MYSQL_ROOT_PASSWORD: secret
 
-  mysql56:
-    image: mysql:5.6
+  mysql80:
+    image: mysql:8.0
     command: [ "--server-id=1", "--log-bin=/var/lib/mysql/mysql-bin.log", "--binlog-format=row"]
     networks:
       default:
         aliases:
-          - mysql56
+          - mysql80
     environment:
-      MYSQL_ROOT_PASSWORD: numtel
+      MYSQL_ROOT_PASSWORD: secret
 
-  mysql57:
-    image: mysql:5.7
+  mysql84:
+    image: mysql:8.4
     command: [ "--server-id=1", "--log-bin=/var/lib/mysql/mysql-bin.log", "--binlog-format=row"]
+    ports:
+      - "3306:3306"
     networks:
       default:
         aliases:
-          - mysql57
+          - mysql84
     environment:
-      MYSQL_ROOT_PASSWORD: numtel
+      MYSQL_ROOT_PASSWORD: secret