Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cleanup our DB

See original GitHub issue

Tell us your idea!

While working on the code, I noticed that we have many unsused columns in our DB. Removing them might improve the performance.

See all added comments in https://github.com/cgeo/cgeo/commit/ff78a2333778a097abd6774cbf680ba70168f8e3

What solution would you suggest?

I would suggest to remove them.

Is there an alternative?

Do nothing.

Additional Information

Issue came up while working on remove reliableLatLon flag in Geocache model (PR #11427)

Issue Analytics

State:
Created 2 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

okainovcommented, Aug 10, 2021

compatibility at least for versions published during the last 12 months

This will unfortunately not work. We cannot remove columns while remaining backwards compatibility. We need to decide.

What do you mean? I think you can keep backward compatibility in the last 12 months and break it for older versions, that’s how I read @moving-bits 's proposal.

Like this: 2016 - Column was added 2017-2018 column was used 2019 - column got deprecated/not used any more. Cleanup the usages so it’s really not used. 2020 - keep it for the sake of compatibility 2021 - remove it completely.

0reactions

fm-syscommented, Oct 14, 2021

Same idea is also mentioned in #651