You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That is your thoughts about possibility to go back to using krowinski/php-mysql-replication library again instead of the moln/php-mysql-replication fork?
The moln fork works great so no big deal. But it seems like moln is falling behind as krowinski/php-mysql-replication seems to be better maintained last months and also have a few new features like krowinski/php-mysql-replication#112 (rows query event).
I don't know exactly what feature was missing/broken in krowinski's library that made you switch to moln, so before I start looking into it maybe you have some information to share. Maybe you can easily see if the problems is resolved in the original package now so laravel-trigger could use it again?
Just afraid moln library might be abandoned as I really love your laravel-trigger package :)
So please share your thoughts, or if you prefer to stay with Moln that would also be interesting to know. I can probably also help with something if needed.
The text was updated successfully, but these errors were encountered:
Yes I can help, but it seems like you were very quick and already tried it? But I can at least test 6.x branch in my projects and see if it works as expected.
Yes I can help, but it seems like you were very quick and already tried it? But I can at least test 6.x branch in my projects and see if it works as expected.
Hello!
That is your thoughts about possibility to go back to using krowinski/php-mysql-replication library again instead of the moln/php-mysql-replication fork?
The moln fork works great so no big deal. But it seems like moln is falling behind as krowinski/php-mysql-replication seems to be better maintained last months and also have a few new features like krowinski/php-mysql-replication#112 (rows query event).
I don't know exactly what feature was missing/broken in krowinski's library that made you switch to moln, so before I start looking into it maybe you have some information to share. Maybe you can easily see if the problems is resolved in the original package now so laravel-trigger could use it again?
Just afraid moln library might be abandoned as I really love your laravel-trigger package :)
So please share your thoughts, or if you prefer to stay with Moln that would also be interesting to know. I can probably also help with something if needed.
The text was updated successfully, but these errors were encountered: