Duplicate organization and repository rows under star history table

[joshenlim]

Bug report

Been noticing a couple of rows with repeated organization and repository name pairs (not too sure if its from testing, but the data in this table is not that important since its a cache so not to worry). I did verify that the updating of the cache is working without inserting new rows though. Two possible solutions:

• Do a check if a row with the organization and repo exists before inserting

• Change PK of the table to be organization and repository to enforce this from the DB

Personally feel that option 2 is more optimal - i guess this is one of the instances which the table editor should support creation of more than 1 PK for a table as well haha

For now, we can do it via the second method by good ol' SQL query

[joshenlim]

odd i was testing this again and it seems like the cacheing wasn't causing any duplication - nonetheless i've created a table with organization and repository forming a composite primary key to enforce this.

if anyone wants do any testing though, i've kept the old stars history table and renamed it as stars_legacy - feel free to use that.