4 ms·
My solution to this is to rename that table/column to “table_deprecated” or “column_deprecated”. This has the nice property of being reversible, causes nice vis
by jlangenauer 6y ago
My solution to this is to rename that table/column to “table_deprecated” or “column_deprecated”. This has the nice property of being reversible, causes nice visible errors if something unanticipated is actually using the column/table, makes it obvious that it shouldn’t be used (well, one would hope), and makes it easy to find for permanent deletion later.
- freedomben 6y agoThat's a great idea! Although I did work with a person once who would use anything that looked helpful regardless of "deprecated" being all over the place (Eclipse would even yell at the method calls but he didn't care). Granted that's Java and at that point in time APIs were being deprecated without workable replacements, so it's hard to fault him.
- symlinkk 6y agoAt that point you might as well just delete them.
- mike-cardwell 6y agoI think you're missing the point. If your migration renames a table or column, then the migration can be rolled back, by simply reversing the rename. If you delete the thing, then there is no way of rolling back other than restoring from backup. I can see it being useful to rename these things, as long as there is some process in place to delete the renamed items after a period of time has passed. Would be good if you could schedule a future migration that will happen only after a certain date has passed, which deletes the renamed tables/columns.