-
Notifications
You must be signed in to change notification settings - Fork 1
feat: introduce basic erd #100
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
Conversation
🦋 Changeset detectedLatest commit: 28f3ce0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Probably we need to normalize person and language within the entries, so we don't have troubles to select and aggregate the data later on. So a relation between ExposureEntry and PersonValue as well as LanguageExposure and LanguageValue needs to be created.
I explicitly didn't add this relation, because custom values will be allowed for both cases. I think it's the easiest way like this. If you have a better idea on how to model this with allowing custom values, let me know. |
No description provided.