Re: Design for storing likes/dislikes?

Hi, Hmm, I'm thinking I might need to go for an enum/choices rather than a NullBooleanField. There are actually four states (so far) that can exist in the relationship between a user and a widget. 1. Like 2. Unlike 3. No vote (i.e. abstain). 4. Not asked yet I suppose I could

Re: Design for storing likes/dislikes?

I've used NullBooleanField for this before, as well. A lot quicker to query on than a ManyToMany, also. On Tuesday, July 16, 2013 9:24:54 PM UTC-4, donarb wrote: > > On Tuesday, July 16, 2013 5:29:47 PM UTC-7, Victor Hooi wrote: >> >> Hi, >> >> We have a list of users, who are going to

Re: Design for storing likes/dislikes?

Hi, I'm leaning more towards NullBooleanField at the moment. There's a number of reasons we're going for binary voting (like/dislike), versus say a star rating. Firstly, rating systems like that are ambiguous - a 2-star rating from me may not be the same as a 2-star rating from somebody else.

Re: Design for storing likes/dislikes?

On Tue, 16 Jul 2013 17:29:47 -0700 (PDT) Victor Hooi wrote: > We have a list of users, who are going to like/dislike various > widgets. > > My question is regarding how to store the like/dislikes. > > Essentially, there can be three states between a user and a widget - >

Re: Design for storing likes/dislikes?

Hi, Cool, didn't know that - thanks =). Performance wise, am I better off creating every single relationship between Users/Widgets as I add users/widgets, and defaulting them to Null then? Or is it better to just add the entries as users like/unlike widgets, and infer the null state from the

Re: Design for storing likes/dislikes?

On Tuesday, July 16, 2013 5:29:47 PM UTC-7, Victor Hooi wrote: > > Hi, > > We have a list of users, who are going to like/dislike various widgets. > > My question is regarding how to store the like/dislikes. > > Essentially, there can be three states between a user and a widget - like, > dislike,

Design for storing likes/dislikes?

Hi, We have a list of users, who are going to like/dislike various widgets. My question is regarding how to store the like/dislikes. Essentially, there can be three states between a user and a widget - like, dislike, and unrated, so it's not just a straight Boolean. I'm thinking of just doing