Rename family in db

[seallard]

Description

This PR renames the actual database table names, foreign keys and constraints to use case instead of family. Pretty high risk PR since the schema changes are not contained in a transaction.

Let me know if you think it should be split into smaller PR:s isolating each schema change.

Fixed

• Rename family to case in database schemas

How to test

• Apply upgrade and downgrade in stage
• Ensure views work

(cg-env) ➜  cg git:(rename-family-in-db) ✗ alembic --config ../alembic-stage.ini upgrade head          
INFO  [alembic.runtime.migration] Context impl MySQLImpl.
INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
INFO  [alembic.runtime.migration] Running upgrade 70e641d723b3 -> b105b426af99, Rename family in db
(cg-env) ➜  cg git:(rename-family-in-db) ✗ alembic --config ../alembic-stage.ini downgrade 70e641d723b3
INFO  [alembic.runtime.migration] Context impl MySQLImpl.
INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
INFO  [alembic.runtime.migration] Running downgrade b105b426af99 -> 70e641d723b3, Rename family in db

This version is a

• PATCH - when you make backwards compatible bug fixes or documentation/instructions

[ChrOertlin]

👍 Nice one question about the order in the alembic script. Looks solid otherwise

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[seallard]

Deployed to vms and Hasta, stage and prod.