Good for 1st question.
For 2nd question, let me see if an example will help make sense.
So far, the community ends up in category with a hive.... name (I'm just guessing from the pattern). So, with a category name like "hive-146513" which maps to the SteemSQL community, I can join the comments table on category that starts with "hive%" to the mapping table to get the community name to get a more meaning information rather than join the Tags table which result in the comments records being displayed multiple.
With the join the tags table, so happen it's displaying multiple records. So, to avoid that, while I joined to tags to search the tag, I don't display the tag and do a DISTINCT on the rest of the select columns.
Hope that helps or not confuse things further. 😎
Good for 1st question.
For 2nd question, let me see if an example will help make sense.
So far, the community ends up in category with a hive.... name (I'm just guessing from the pattern). So, with a category name like "hive-146513" which maps to the SteemSQL community, I can join the comments table on category that starts with "hive%" to the mapping table to get the community name to get a more meaning information rather than join the Tags table which result in the comments records being displayed multiple.
With the join the tags table, so happen it's displaying multiple records. So, to avoid that, while I joined to tags to search the tag, I don't display the tag and do a DISTINCT on the rest of the select columns.
Hope that helps or not confuse things further. 😎
Ah, thanks. I was looking through the views and didn't see the communities ones yesterday.
Good to experiment bit