Posted by Erwin Moller on 01/24/08 09:39

Neeper wrote:
> 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.
>
> 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.
>
> 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.
>
>
> Please give me your thoughts.

Hi,

If the application is classified, as you wrote in your first post, you
might also consider using different databases for each city, with
different username/passwords.
If you don't, you should make very sure city1 cannot access data for
city2, eg by doing getname.php?cityid=2 or something like that.

To your question, if you use an index on the relevant columns on the
table, the queries are probably very fast, IF you use that indexed
column in your where-clause.

Regards,
Erwin Moller


>
>
> Thanks.

[Back to original message]