Right now, every url is added to db with new id. There is no checking to see if the url has been read before. Our "readings" table should only add rows for new articles, and for previously read articles, we can just add the appropriate ids to the "user readings" table. This would mean comparing entire url strings, which I doubt is very performant.
aubundy
commented
2 years ago 
Right now, every url is added to db with new id. There is no checking to see if the url has been read before. Our "readings" table should only add rows for new articles, and for previously read articles, we can just add the appropriate ids to the "user readings" table. This would mean comparing entire url strings, which I doubt is very performant.