@rene thanks! I tried to clarify the idea - while I always assumed the Posts.Tags column is standalone, I did not mean that other tables are derived from it, just got too focused on the context of the question (post tags) and forgot to add the other 2 tables
@rene flattered :) I am still not sure if the post shouldn't have been split in 2 as I can see it asking 2 somewhat unrelated questions
Yeah, I imagine people will go `where post,tags like '%<java>%' and while that might lead to success you better use the other relations in that case. So that is why I prefer to at least mention that structure.
Still not sure how SEO and tags will influence btw
@rene would you say it's generally faster to query the Tags table for the name match, then use the id to lookup the post id in the PostTags table and then join it in with the Posts table?
@rene huh, yeah. I've seen mutliple reports on Google's search showing very weird results (like 0 instead of the title), but staff claims that microdata is correct
@rene hmm, yes, that makes sense - should be indeed faster