Dude, that just tells you if the table is used on the happy path. It does not tell you if it's only used by a customer whose godson is the CEO's favorite kid. Or if customers only use it right before a federal deadline for filing forms, or at the end of the quarter when it's time to generate reports. Which you didn't collect for 2 months.
Re:Safely Dropping MySQL Tables
by dotancohen on Tuesday July 26, 2022 @02:28AM
(#32235039)
> Or if customers only use it right before a federal deadline for filing
> forms, or at the end of the quarter when it's time to generate reports.
I personally like to version my APIs, but that is robust insofar as code changes, not for database changes.
The other responder liked monorepos for this. Itβs not perfect, but it does help with making sure you had all of the code to search from, and once in a while the commit history adds additional clues.
Into the repo method, push up the change, redeploy the projects that depend on the library and wait a while and grep the logs to see if it ever gets used.
Monorepo is easier though.