|
Posted by Jerry Stuckle on 01/24/08 11:53
Jerry Stuckle wrote:
> 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.
>>
>>
>> Thanks.
>>
>
> For MySQL questions, try comp.lang.mysql. That's what it's there for.
>
Uh, that should be comp.databases.mysql :-)
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|