Home/ Questions/Q 9040767
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-16T10:04:28+00:00

Well im working on an online game project where every player will get to

  • 0

Well im working on an online game project where every player will get to have a house, the project was going great until u had to organize houses thinking that i will have a limit of 10.000 players on the server.

so here are some facts:

each player may have up to 10 houses (min 1).
that means i need 100.000 possible houses so that no matter how full the server gets, there will always be 10 possible houses for each player.

there will be 20 cities, each city will have 200 neighborhoods, and each neighborhood will have 25 houses

so thats when the problem shows up, how would the database work?

whenever i want to see any of the 100.000 houses, it will belong to a neighborhood on a city, and i need to be able to play with that, like if i want to see house #5 of the neighborhood #123 city#8, then i should be able to get the data.

i was thinking about having one table with all 100.000 houses, and having values on that table to tell what neighborhood it is on what city, but it feels like there must be a better way. (maybe using multiple tables? i dont know)

so any help would be appreciated.

thank you for your time.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It’s hard to answer, because your complete requirements aren’t known.

    But I’d recommend that you normalize the database – 3rd normal form at minimum. If you don’t know what that is, I’d recommend learning about it ASAP.

    My best guess is as follows:

    1. PLAYER is one-to-many with HOUSE. If more than one PLAYER owns the same HOUSE, then it’s many-to-many.
    2. CITY is one to many with NEIGHBORHOOD
    3. NEIGHBORHOOD is one-to-many with HOUSE

    You’ll do JOINS to associate a PLAYER with cities, neighborhoods, and houses. You should have surrogate primary keys on all tables and appropriate foreign keys. Add UNIQUE indexes on all other candidate key combinations.

    Run EXPLAIN PLAN on all your queries to make sure that they don’t require TABLE SCAN and perform adequately.

    10,000 players isn’t a big number for a database. You won’t have any problem.

    Here’s what your query to select all the houses in a neighborhood might look like: 

    SELECT *
FROM HOUSE H
INNER JOIN NEIGHBORHOOD N
ON H.HOUSE_ID = N.HOUSE_ID
INNER JOIN CITY C
ON N.NEIGHBORHOOD_ID = C.NEIGHBORHOOD_ID
WHERE C.CITY_ID = 8
AND N.NEIGHBORHOOD_ID = 123
ORDER BY H.HOUSE_ID
    • 0