-
Notifications
You must be signed in to change notification settings - Fork 85
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
BREAKING CHANGES: Update database schema #111
Comments
Based on our conversation below is a model of the current Model: https://dbdiagram.io/d/61d360353205b45b73d55971 Considerations
Todo
ChangelogAdded
Changed
|
id
; change obdb_id
to slug
@alexjustesen This is more of what I'm thinking about with the schema (I also updated the v1 to be more based on reality): https://dbdiagram.io/d/61d3c9533205b45b73d5a738
We still have the "key problem" you mention in your third TODO. I guess just another UUID? Would be nice to have it be shorter. Maybe something based on lat/lng or would that be dumb? |
Oh, and after thinking about it, the whole "slug" thing should be handled programmatically or in a mapping table. Seems a little silly to hard-code it here. |
I agree, the slug for SEO purposes should be generated off the name where it's being used. |
I removed |
@alexjustesen Sounds good! I think the whole |
I think you're right, I'll switch it back |
Tasks
obdb_id
toslug
id
to use UUIDNotes
The text was updated successfully, but these errors were encountered: