It's hard to understand the current DB tables schema from the code alone. Switching between the testing/prod database or migrations doesn't look quite right: migrations are fine while there are a few of them.
Writing DB tables spec can be beneficial:
a single source of data models for the current state of DB tables
It's hard to understand the current DB tables schema from the code alone. Switching between the testing/prod database or migrations doesn't look quite right: migrations are fine while there are a few of them.
Writing DB tables spec can be beneficial: