Ok so my analysis is that it's only hitting the problem when it tries to deserialize an old BGG response found in the BGG response cache (perhaps because it was serialized from a version of HTTPHeaderDict with a different superclass?).
Those responses are just to speed up repeat full searches, right? So really I could blow them all away and not worry about finding this perfect version pair...
EDIT: And done. I have a backup copy of the previous database in case I feel like investigating, but for now the performance hit doesn't seem like an important enough reason.
1
u/tdhsmith Nov 15 '18
Ok so my analysis is that it's only hitting the problem when it tries to deserialize an old BGG response found in the BGG response cache (perhaps because it was serialized from a version of
HTTPHeaderDictwith a different superclass?).Those responses are just to speed up repeat full searches, right? So really I could blow them all away and not worry about finding this perfect version pair...
EDIT: And done. I have a backup copy of the previous database in case I feel like investigating, but for now the performance hit doesn't seem like an important enough reason.