Tag Info

Ask 1 (specific researched non-duplicate) question. https://stackoverflow.com/tour https://stackoverflow.com/help/how-to-ask https://stackoverflow.com/help

I went with your suggestion of "A combined unique key on game id + game name". And FYI unfortunately names can be repeated. Some examples include "Wizard" and "Samurai".

A combined unique key on game id + game name would make sense, if you want to prevent that you insert the same data twice. If the game ID for "The Settlers of Catan" is 37, and you already ...

Thanks but, while I know that making a primary key using both columns is considered best practice, I'm just not sure why. For my other tables, I can see the primary key helps with joins or quick ...

site:stackoverflow.com how to decide on primary key

This site uses English please.

best approach store your 5M ids in Log or ReplicatedMergeTree table in all servers then use id IN (SELECT id FROM ids_table) 5M ids is not so much, and if you use http+gzip encoding it could be 5-15M ...

Nothing in the absurd discussions functionality changes what "a" question is. It allows a larger range of questions. I have made no mistake. PS Re magic links: Yeah I keep thinking this is ...

Actually @PhilipXY this is one of the new "discussion" questions (this one is a "Best Practises") and as such does not need to ask a single specific question like a regular Q&A ...

Ask 1 (specific researched non-duplicate) question. https://stackoverflow.com/tour https://stackoverflow.com/help/how-to-ask https://stackoverflow.com/help How much research effort is expected of ...

You seem to have two columns in the tourinfo table that seem to store multiple data points as column value. You should normalise those columns. Besides these, it is pretty difficult to comment on a ...

I would use these tables as a starting point: tooltips id, page_id, title, content, selector, position, etc. tours id, title, etc. tour_tooltips id, tour_id, tooltip_id, index_order This allows for ...