There are 1084 podcasts in the index that have multiple entries for the same itunesId. To take one example, there are 3 podcasts with the same itunesId 1436402852:
sqlite> select id, newestItemPubdate, episodeCount, lastHttpStatus, dead, url, originalUrl from podcasts where itunesId = 1436402852;
id|newestItemPubdate|episodeCount|lastHttpStatus|dead|url|originalUrl
1149309|1602073500|25|404|0|https://nerdylegion.com/podcasts/batpod.rss|https://nerdylegion.com/podcasts/batpod.rss
1335771|1621076400|56|404|0|https://feeds.buzzsprout.com/1402636.rss|https://feeds.buzzsprout.com/1402636.rss
1393509|1702234800|112|200|0|https://anchor.fm/s/36435d74/podcast/rss|https://anchor.fm/s/36435d74/podcast/rss
It might be useful to have a UNIQUE constraint on the itunesId column since it is hard to think of a reason for keeping the first two rows in storage.
There are 1084 podcasts in the index that have multiple entries for the same itunesId. To take one example, there are 3 podcasts with the same itunesId 1436402852:
It might be useful to have a UNIQUE constraint on the itunesId column since it is hard to think of a reason for keeping the first two rows in storage.