You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Related to issue 151 and issue 157.
Describe the solution you'd like
The endpoint requires an array of hashtag names as well as the user id.
Create a table called UserInterests in the form of
(PK) ID: INTEGER
(FK) USER_ID INTEGER
(FK) TAG_ID: INTEGER
Constraint: Unique(USER_ID, TAG_ID)
Add these tags for the user id into the table.
Describe alternatives you've considered
The endpoint could accept tag ids instead of names which would mean we would not have to query the tag table in the database to find the TAG_ID.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Related to issue 151 and issue 157.
Describe the solution you'd like
The endpoint requires an array of hashtag names as well as the user id.
Create a table called UserInterests in the form of
(PK) ID: INTEGER
(FK) USER_ID INTEGER
(FK) TAG_ID: INTEGER
Constraint: Unique(USER_ID, TAG_ID)
Add these tags for the user id into the table.
Describe alternatives you've considered
The endpoint could accept tag ids instead of names which would mean we would not have to query the tag table in the database to find the TAG_ID.
The text was updated successfully, but these errors were encountered: