Timeline for How do you document your databases?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 10, 2016 at 3:49 | history | edited | RolandoMySQLDBA | CC BY-SA 3.0 |
added 8 characters in body
|
| Jul 12, 2013 at 15:07 | history | made wiki | Post Made Community Wiki by jcolebrand♦ | ||
| Aug 19, 2011 at 20:24 | comment | added | Nick Chammas | A big problem I find with documentation that is not bound closely to the code (e.g. a separate Word document, as opposed to an auto-generated schema diagram + well-named database objects) is that this documentation is guaranteed to be flat out wrong as time passes. The reason is simple: a separate document effectively duplicates information. Without an automated way to keep it in sync with the source, it will become obsolete very quickly. Compare this to a tool that generates a schema diagram live from the database and pulls the appropriate comments from within the code. | |
| Jan 11, 2011 at 14:10 | history | answered | Tangurena | CC BY-SA 2.5 |