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
Just read the sources and found that in this crate, the RotateEvent change of tables id is not managed.
Can lead to some data-corruptions, it's mostly a problem when doing networked binlog usage, may be out-of-scope if the goal is just following binlog files. table_id are memory id persistent only during the server is running.
Hi!
Just read the sources and found that in this crate, the
RotateEvent
change of tables id is not managed.Can lead to some data-corruptions, it's mostly a problem when doing networked binlog usage, may be out-of-scope if the goal is just following binlog files.
table_id
are memory id persistent only during the server is running.See for details:
https://github.com/julien-duponchelle/python-mysql-replication/blob/1376c6be032a46b396c6991133b958271604e829/pymysqlreplication/binlogstream.py#L507-L521
The text was updated successfully, but these errors were encountered: