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
Copy file name to clipboardExpand all lines: CHANGELOG
+39-4
Original file line number
Diff line number
Diff line change
@@ -84,7 +84,7 @@
84
84
* PyMYSQL 0.7
85
85
* Add more contributors
86
86
87
-
0.10 30/11/2016
87
+
0.10 30/11/2016
88
88
* row-events: TIME is now encoded as python.timedelta
89
89
* Allow users to define ctl_connection_settings and the option to fail when table information is unavailable (#176)
90
90
* Decode gtid from network packet
@@ -128,7 +128,7 @@
128
128
129
129
0.19 29/04/2019
130
130
* Fix Insert NULL in a boolean column returns no rows #288
131
-
* Added empty string support for enum
131
+
* Added empty string support for enum
132
132
* Fix column order
133
133
* Fix float problem about time fieldtype
134
134
@@ -168,7 +168,7 @@
168
168
* Add support for MariaDB GTID
169
169
170
170
0.29 08/04/2022
171
-
* Skip db name parsing if mts_accessed_dbs == 254
171
+
* Skip db name parsing if mts_accessed_dbs == 254
172
172
173
173
0.30 28/04/2022
174
174
* Fix decoding large json arrays
@@ -195,4 +195,39 @@
195
195
* Fix release error
196
196
197
197
0.43.0 23/07/2023
198
-
* Bump PyMySQL to 1.1.0 to solve : LookupError: unknown encoding: utf8mb3
198
+
* Bump PyMySQL to 1.1.0 to solve : LookupError: unknown encoding: utf8mb3
199
+
200
+
0.44.0 12/09/2023
201
+
* Add MariadbAnnotateRowsEvent
202
+
* Add RandEvent
203
+
* Add MariadbStartEncryptionEvent
204
+
* Add RowsQueryLogEvent
205
+
* Add MariadbBinLogCheckPointEvent
206
+
* Add PreviousGtidsEvent
207
+
* Add UserVarEvent
208
+
* Fix Bug increase history list length and snapshot : Mysql 8.0 version connection was being created along with the opening of a transaction. This led to a problem with looking at the snapshot before creating the table
209
+
* Fix Avoid UnicodeDecodeError for non-utf8 QueryEvents
210
+
* Enhance Data Integrity with Binlog Event Checksum Verification
Firstly, thank you for considering to contribute to `python-mysql-replication`. We appreciate your effort, and to ensure that your contributions align with the project's coding standards, we employ the use of `pre-commit` hooks. This guide will walk you through setting them up.
4
+
5
+
## Setting up pre-commit
6
+
7
+
1.**Install pre-commit**
8
+
9
+
Before you can use `pre-commit`, you need to install it. You can do so using `pip`:
10
+
11
+
```bash
12
+
pip install pre-commit
13
+
```
14
+
15
+
2.**Install the pre-commit hooks**
16
+
17
+
Navigate to the root directory of your cloned `python-mysql-replication` repository and run:
18
+
19
+
```bash
20
+
pre-commit install
21
+
```
22
+
23
+
This will install the `pre-commit` hooks to your local repository.
24
+
25
+
3.**Make sure to stage your changes**
26
+
27
+
`pre-commit` will only check the files that are staged in git. So make sure to `git add` any new changes you made before running `pre-commit`.
28
+
29
+
4.**Run pre-commit manually (Optional)**
30
+
31
+
Before committing, you can manually run:
32
+
33
+
```bash
34
+
pre-commit run --all-files
35
+
```
36
+
37
+
This will run the hooks on all the files. If there's any issue, the hooks will let you know.
38
+
39
+
## If you encounter issues
40
+
41
+
If you run into any problems with the hooks, you can always skip them using:
42
+
43
+
```bash
44
+
git commit -m "Your commit message" --no-verify
45
+
```
46
+
47
+
However, please note that skipping hooks might lead to CI failures if we use these checks in our CI pipeline. It's always recommended to adhere to the checks to ensure a smooth contribution process.
48
+
49
+
---
50
+
51
+
That's it! With these steps, you should be well on your way to contributing to `python-mysql-replication`. We look forward to your contributions!
0 commit comments