Posted by Ivan Marsh on 01/24/08 19:02

On Thu, 24 Jan 2008 06:00:31 +0000, Neeper wrote:

> I'm creating a classifieds 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.

Read up on "Database Normalization" and your question will answer itself.

--
I told you this was going to happen.

[Back to original message]