🕸Fergus Duniho wrote on Sat, Mar 10, 2012 02:52 AM UTC:
We have that already. It is called Recognized Variants. But it takes effort
to add to it, and it is not as responsive to user preferences.
For the technically inclined, here is the table I'm thinking of adding:
create table Likes (
UniqID blob,
ItemID blob,
UserID blob,
Freq tinyint,
Rating tinyint,
primary key(UniqID),
key (ItemID, UserID)
);
The UniqID will be a concatenation of ItemID with UserID, and its purpose
is to uniquely identify a row for quick reading and writing. The other two
keys, ItemID and UserID, may have the same value for multiple rows and are
included for finding all rows with the same ItemID or the same UserID. The
remaining two values include integers representing answers to the two
questions.
We have that already. It is called Recognized Variants. But it takes effort to add to it, and it is not as responsive to user preferences. For the technically inclined, here is the table I'm thinking of adding: create table Likes ( UniqID blob, ItemID blob, UserID blob, Freq tinyint, Rating tinyint, primary key(UniqID), key (ItemID, UserID) ); The UniqID will be a concatenation of ItemID with UserID, and its purpose is to uniquely identify a row for quick reading and writing. The other two keys, ItemID and UserID, may have the same value for multiple rows and are included for finding all rows with the same ItemID or the same UserID. The remaining two values include integers representing answers to the two questions.