Commit e0451ce
committed
Use WAL with SQLite cache, fix close
This is the more modern way to manage concurrency with SQLite
In our case, it means concurrent mypy runs using the cache will wait for
each other, rather than fail
SQLite also claims this is faster, but I haven't yet done a good profile
(If you are profiling this, note that WAL is a persistent setting, so
you will want to delete the cache)
Finally, I also explicitly close the connection in main. This is
relevant to this change, because it forces checkpointing of the WAL,
which reduces disk space and means the cache.db remains a single
self-contained file in regular use1 parent ef7e8a6 commit e0451ce
2 files changed
+13
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
189 | 189 | | |
190 | 190 | | |
191 | 191 | | |
| 192 | + | |
| 193 | + | |
| 194 | + | |
| 195 | + | |
| 196 | + | |
| 197 | + | |
192 | 198 | | |
193 | 199 | | |
194 | 200 | | |
195 | 201 | | |
196 | 202 | | |
197 | 203 | | |
198 | 204 | | |
199 | | - | |
| 205 | + | |
200 | 206 | | |
201 | 207 | | |
202 | 208 | | |
| |||
227 | 233 | | |
228 | 234 | | |
229 | 235 | | |
| 236 | + | |
| 237 | + | |
| 238 | + | |
| 239 | + | |
230 | 240 | | |
231 | | - | |
| 241 | + | |
232 | 242 | | |
233 | 243 | | |
234 | 244 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
163 | 163 | | |
164 | 164 | | |
165 | 165 | | |
| 166 | + | |
166 | 167 | | |
167 | 168 | | |
168 | 169 | | |
| |||
0 commit comments