That means that every node on the network will need to re-download the blockchain if they upgrade to 0.5.2 Can't there be a patch or script you can release to "fix" the table problem?
In my case, my pool runs two nodes and a test server. I will have to re-download for each server. At this point, I'll probably just wait until the next release.
Right.. And that's one of the reasons why we did not release the server package, but just the client.
There is one comfort however, the new version uses websockets instead of http for peer connections so it downloads much faster.
I'll see what i can do but I cannot spend days on this when the handfull of nodes on the network can download a new blockchain in a matter of hours.
If it's any comfort this will likely not happen future.