Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enrich our DB model #30

Open
goldbergyoni opened this issue Dec 8, 2020 · 2 comments
Open

Enrich our DB model #30

goldbergyoni opened this issue Dec 8, 2020 · 2 comments
Assignees
Labels

Comments

@goldbergyoni
Copy link
Contributor

The example app DB schema is too simplistic and might not tell the truth when conducting performance benchmarks. It could be great to add a few more fields to the main table and also one more relation.

Before picking this issue, it's recommended to have a short tech planning chat here and only then upon sync to get up to speed.

@goldbergyoni goldbergyoni added the good first issue Good for newcomers label Dec 8, 2020
@goldbergyoni
Copy link
Contributor Author

There are levels of data that we should have:

  • Test data - Orders - Rows that are modified by the tests - Created per test - We have this
  • Context - StoreInfo - Rows that are related to the test but not modified by the test - Created per suite - We need this
  • Metadata - Countries - Rows that just serve as global enums and supporting data - Created once - We need this

@philipeatela
Copy link

@goldbergyoni @DanielGluskin Is this still an issue/was this ever worked on?

I'm interesting in contributing to this repo, since it did so much for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants