Open AndreasChristianson opened 3 years ago
This was to enable us to capture more accurate data, and also extend in the future. Example of the current problem:
We have one table currently, it is basically a table of commits. When we decided to start capturing data on file extensions changed, we now have no way to tie each extension to an actual number of files changed. We simply have total files changed, and a distinct list of extensions that were affected. If we were to break our table structure out we would be able to actually record more detailed info about each commit, including specific number of files changed, and any future data that fits in to things like that.
Definitely not a short term need, just something I wanted to make sure we had an eye on.
@GeneTinderholm @grey-lovelace , I don't remember what this was about