-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat(recommendation): add enum and tables needed for event recommenda… #53
base: master
Are you sure you want to change the base?
Conversation
What's missing:
|
src/deploy/table_user_interest.sql
Outdated
BEGIN; | ||
|
||
CREATE TABLE maevsi.user_interest ( | ||
user_id uuid NOT NULL REFERENCES maevsi.account(id) ON DELETE CASCADE, |
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.
Let's call it account_id
(it should be called account_id
in all other places currently)
src/deploy/enum_event_category.sql
Outdated
|
||
BEGIN; | ||
|
||
CREATE TYPE maevsi.event_category AS ENUM ( |
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.
Let's create a table for that, so some administrators can change the list via some content management system in the future without having to change the database code.
Enum type event_category replaced by table of the same name. Policies modified. Table and column comments added.
File names changed to be in accordance with table name.
Added the enum and tables required for the event recommendation. Not sure how to implement the tree structure for subcategories.