Skip to content

Improve table naming in SQL Databses #161

Description

@dmytro-kashcheiev

Issue:
I have sompackage.WatchedEmployees projection for a while. After a big update with the migration procedure now I have a someNEWpackage.WatchedEmployees projection fulfilled with the similar data. I've decided to clean up the Database from the outdated projection states.

And now in the Database, I see two tables:
WatchedEmployeesProjection_121113123123 and WatchedEmployeesProjection_664398 and it's impossible to determine what projections are represented by these tables. Probably situation will get even worse when there will be two different projections with the same name (for example in different Bounded Contexts).

Possible solutions

  • put the state's package name in the table name (like it is in Datastore);
  • add table that stores mapping with package.EntityState <-> Table Name;
  • something else.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions