Note that there are some explanatory texts on larger screens.

plurals
  1. POHow inefficient would this query be and also table structure?
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COWhat information exactly do you want to display for `course_updates` and what information exactly do you want to display for `follower_updates`?
      singulars
    2. COFor course updates, I'm simply storing whenever a user adds or removes a course. So I store a course id and a uID as well as the action. As for follower updates, I'm storing information regarding who follows who when. I'm finding out that I won't be able to align my columns. I'm thinking that I may switch to a different table structure where I have updates, user_updates and course_updates. course_updates will store the course number timestamp and an id reference to the updates table where I will have an updateObject stored via json. This will lead to data redundancy in the database though.
      singulars
    3. COThe data redundancy will occur because I will need to store data in the course updates for the user adding a course, but I'd also have to store the same information in the user_updates table in order to get the same information if a user is following someone. Ultimately, a nosql solution would probably be best, but I'm trying to stick to SQL. I'm not sure how exactly to lay everything out. As is I would need to add a user_update for both users when one followed the other to be able to get the information when I queried the database.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload