> a three-ring binder called the Prompt File, stuffed with printouts of the dozens of tables in the system, and religiously updated anytime anyone changed anything of significance.
Well, as a DBA, I periodically use a 3rd party tool to print out the schema. It's mainly for new hires to learn from.
But sometimes I'll flip through it and notice:
- mis-spelled table names, usually duplicate tables
- missing FKs
- missing unique keys, most commonly for early RoR apps
- developer-specific EAV tables with 1 row.
The benefit always outweighs the dead trees, but printing once a year is typical. Back in the day, more frequenctly on 25-line terminals where there was too much scrolling.
praptak|4 years ago
Necessity is the mother of documentation.
taneq|4 years ago
choeger|4 years ago
redis_mlc|4 years ago
But sometimes I'll flip through it and notice:
- mis-spelled table names, usually duplicate tables
- missing FKs
- missing unique keys, most commonly for early RoR apps
- developer-specific EAV tables with 1 row.
The benefit always outweighs the dead trees, but printing once a year is typical. Back in the day, more frequenctly on 25-line terminals where there was too much scrolling.
praptak|4 years ago