Commit b500ad4
authored
use consistent read when deleting data (#171)
### TL;DR
Added `ForceConsistentData: true` to query filters in block deletion operations.
### What changed?
Modified the query filters in `deleteBlocks`, `deleteLogs`, `deleteTransactions`, and `deleteTraces` functions to include `ForceConsistentData: true` parameter when retrieving data before deletion.
### How to test?
1. Attempt to delete blocks and their associated data
2. Verify that the deletion operations complete successfully
3. Confirm that all related data (logs, transactions, traces) is consistently deleted
### Why make this change?
Ensures data consistency during block deletion operations by forcing the query to return complete and consistent datasets before performing deletions. This prevents potential partial or inconsistent data deletions that could corrupt the database state.1 file changed
+12
-8
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1039 | 1039 | | |
1040 | 1040 | | |
1041 | 1041 | | |
1042 | | - | |
1043 | | - | |
| 1042 | + | |
| 1043 | + | |
| 1044 | + | |
1044 | 1045 | | |
1045 | 1046 | | |
1046 | 1047 | | |
| |||
1055 | 1056 | | |
1056 | 1057 | | |
1057 | 1058 | | |
1058 | | - | |
1059 | | - | |
| 1059 | + | |
| 1060 | + | |
| 1061 | + | |
1060 | 1062 | | |
1061 | 1063 | | |
1062 | 1064 | | |
| |||
1071 | 1073 | | |
1072 | 1074 | | |
1073 | 1075 | | |
1074 | | - | |
1075 | | - | |
| 1076 | + | |
| 1077 | + | |
| 1078 | + | |
1076 | 1079 | | |
1077 | 1080 | | |
1078 | 1081 | | |
| |||
1087 | 1090 | | |
1088 | 1091 | | |
1089 | 1092 | | |
1090 | | - | |
1091 | | - | |
| 1093 | + | |
| 1094 | + | |
| 1095 | + | |
1092 | 1096 | | |
1093 | 1097 | | |
1094 | 1098 | | |
| |||
0 commit comments