Database evolution for a future version of Vienna (v4)

[barijaona]

This discussion has been opened to note possible improvements to database design.

These changes might include:

• more robust definition of smart folders (cf. Make folder selection in smart folders more robust #1906 discussion)
• per folder filters (All articles / Unread Articles / Flagged / Today…) instead of having the same filter apply everywhere: this would be especially useful for smart folders, where filtering might contradict the goal of the smart folder (issue View/Filter By is alway applied even in Smart Folder #218)
• per feed setting for "Mark updated articles as new"
• more presentation options for each feed (in addition to the current "Use Web Page for Articles" , something similar to Safari Reader View would be nice)

[Eitot]

• A separate table for enclosures, to allow for multiple enclosures per feed item (which Atom and JSONFeed support), optionally also supporting fields like MIME type and expected byte size (both of which may be provided by the feed, including RSS)
• "Modern" SQLite3 features like foreign keys to establish relationships between tables, e.g. to "cascade" row updates/deletions to dependent rows in other tables

[barijaona]

I would also like to be able to have different purge policies according to types of feeds.

[barijaona]

And be able to have different settings for "Mark updated articles as new"