You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be helpful to be able to tag/filter posts (separately from Entry-Type); Entry-Type generally is used only for affecting layout/visibility, whereas tags are used for filtering with one or more attributes. (For example, in a comic, being able to tag entries based on characters or subject matters.)
An efficient strategy for implementing this would start with adding Tag and EntryTag columns to the database, where Tag provides the plaintext strings and EntryTag associates them with the entry. When an entry is scanned its EntryTag associations would be destroyed before the existing ones are added. Adding the appropriate joined expression to the view query is not something I want to think about right now.
The text was updated successfully, but these errors were encountered:
Is there any reason to normalize tags? I don't think there is; columns can just be EntryID, TagString. TagString could probably be stored/searched as its .lower(), even.
It'd be helpful to be able to tag/filter posts (separately from
Entry-Type
);Entry-Type
generally is used only for affecting layout/visibility, whereas tags are used for filtering with one or more attributes. (For example, in a comic, being able to tag entries based on characters or subject matters.)An efficient strategy for implementing this would start with adding
Tag
andEntryTag
columns to the database, whereTag
provides the plaintext strings andEntryTag
associates them with the entry. When an entry is scanned itsEntryTag
associations would be destroyed before the existing ones are added. Adding the appropriate joined expression to the view query is not something I want to think about right now.The text was updated successfully, but these errors were encountered: