|
Posted by Michael Fesser on 01/25/08 19:04
..oO(Neeper)
>I'm creating an application for multiple cities (about 20-50 cities).
>I'm not sure whether to use a single table to store for all cities'
>items or break each one out into a seperate table for each city.
One table.
>I know a seperate tables will be faster for searches because there
>will be less records but in terms of maintenance it gets a little
>messy and hectic as the list of cities will grow.
There won't be much of a difference if the tables are properly indexed.
>I guess it all comes down to is, the number of records I would have.
>I'm not sure how many records it takes before MySQL starts to slow
>down.
Millions.
Micha
Navigation:
[Reply to this message]
|