)

* Fix for negative number handling (DECIMAL -51.1234 could not read). This seems to fix it.
Inspired by fengxiangyun/mysql-replication@a9da836

typo

…array with small numbers (#96)

Thank you

* - Change: drop support for < 8.2
- Change: moved to enums, promoted properties
- Added: logger for more socket info
- Added: slave_uuid support
- Change: config no longer static
- Chore: typos in README/code
- Chore: replace/remove old urls from code
- Chore: changed variables to underscore
- Added: support caching_sha2_password
- Change: BinLogServerInfo static calls removed also added method getServerInfo to MySQLReplicationFactory

* Remove symfony/dependency-injection dependency - it is unused

* Enable backward compatibility to symfony 6

…checkTablesOnly` (#129)

Co-authored-by: Deeka Wong <[email protected]>

* Updating workflow

* Add query for MySQL 8.4

* fix #115 for mysql 8.0.0

* fix #115 for mysql 8.4.0

* fix #115 for mysql 8.4.0 phpunit test

* fix issue #125

* change to hetao29

* Fix PHP 8.4 deprecation: Implicitly marking parameter as nullable is deprecated, the explicit nullable type must be used instead

* change to krowinski

* Fix maintainer feedback: always return strings from readInt64/unpackUInt64

- Changed readInt64() to always return string instead of string|int
- Changed unpackUInt64() to always return string instead of string|int
- Changed readUInt64() return type to string for consistency
- Applied code style fixes with composer cs:fix
- Fixes failing tests: testShouldReadInt64 and testShouldPack64bit

Addresses maintainer feedback from PR #116 regarding MySQL 8.4.0 compatibility.

* Fix DBAL 4.x compatibility issue in testShouldReconnect

In DBAL 4.x, Doctrine\DBAL\Exception became an interface instead of a concrete class.
The test was trying to instantiate 'new Exception('')' which fails with
'Cannot instantiate interface Doctrine\DBAL\Exception'.

Fixed by using ConnectionException mock which implements the Exception interface,
preserving the exact same test logic and coverage as the original DBAL 3.x version.

* Fix MySQLRepository for DBAL 4.x compatibility

Remove manual connection reconnection logic since DBAL 4.x handles
reconnection automatically. The connect() method became protected
in DBAL 4.x, causing 'Call to protected method' errors.

Changes:
- Removed manual ping/close/connect logic from getConnection()
- DBAL 4.x automatically handles lost connections and reconnection
- Kept ping() method as required by PingableConnection interface

This fixes the repository to work with DBAL 4.x while maintaining
the same functionality.

---------

Co-authored-by: hetao <[email protected]>
Co-authored-by: HeTao <[email protected]>