191 reputation
310
bio website
location
age
visits member for 3 years, 6 months
seen Nov 22 at 13:13

Nov
18
comment Best design to handle multiple query keys
OK, I go suggested way. Thank you everybody for your input.
Nov
18
accepted Best design to handle multiple query keys
Nov
6
comment Best design to handle multiple query keys
One table - this is requirements that I cannot change.
Nov
6
comment Best design to handle multiple query keys
@dezso If it is not "classical" approach that we all used to stick with it doesn't mean it will result with awful performance.
Nov
6
comment Best design to handle multiple query keys
Solution from Michael is a classic one. You can find it in any book. But I doubt it will work well on the huge data.
Nov
6
comment Best design to handle multiple query keys
@ypercube for me that mean that you don't have experience with problems I mentioned. I DO KNOW about technique you described, but it doesn't work well on fast growing data. This is why I asked about other approach. Let's stop off-topic discussion and stick to the subject. I need a tip for the person who knows the problem. This is not question for guys that just know PostgreSql or have some ex with it. I know that other company does it with one table and it works very fast.
Nov
6
comment Best design to handle multiple query keys
@ypercube Guys, if you have nothing to say on the topic please pass by. I am really not forcing you to reply. This is not an exam. No answer - no need for reply. Thank you for understanding.
Nov
6
comment Best design to handle multiple query keys
@dezso As I mentioned in the question, I want to have only one table, so, there is no place for "normalization" in my opinion. By using "normalization" I would expect to have several tables with references by ids. So, could you please clarify what do you mean by "normalization", so your reply will be useful for me and for community?
Nov
6
comment Best design to handle multiple query keys
@ErwinBrandstetter I just added typical query. Further sorting is not relevant - I can do it in another subquery - my main question is - how to organize selection by Player-Id without extra tables. Thank you for your attention.
Nov
6
awarded  Commentator
Nov
6
comment Best design to handle multiple query keys
@dezso Lets see what other say. I think PostgreSQL is a right platform, I just have to find a proper way to do it. I am sure there is a good technique for my task.
Nov
6
comment Best design to handle multiple query keys
@ErwinBrandstetter, I added that player might be interested in most in last XXX of his games. Sorting and form of the data is not subject of my question.
Nov
6
comment Best design to handle multiple query keys
Normalization won't work for me. If you are interested, please see accepted question on SO. I will try to go with like.
Nov
6
awarded  Citizen Patrol
Nov
5
asked Best way to handle multiple query keys
Nov
5
comment Best design to handle multiple query keys
Each key corresponds to a json_data. There is no such a think as a key combination. Every time it can be any keys.
Nov
5
asked Best design to handle multiple query keys
Jul
15
awarded  Taxonomist
Jun
25
awarded  Notable Question
Apr
8
awarded  Nice Question