MySQL Lists are EOL. Please join:

List:General Discussion« Previous MessageNext Message »
From:Sean Hynes Date:June 23 1999 9:10pm
Subject:Re: Yellow Page Setup
View as plain text  
Thank you very much for the quick response and help! 

Maybe creating a table per state would be in order, because the data could
easily get up to 1,000 records per city.
If we use major metropoliton cities, there probably won't be many multiple
city searching. That won't be a funcition of 
a query anyway.
So what is the majic number to switch to seperate tables maybe around 1,000
per table?
 What else would be a reason for looping across multiple tables?

Thanks again for advice! You da man!

>I have to disagree with Sasha's advice. With the limited amount of data in
>each table, 100 records per table, there should be no serious performance
>problem to put all the records in one table. The added advantage is that
>You can perform searches across city borders without expensive table
>reopenings in the server and complicated looping across multiple tables in
>Your script code.
>I'm storing share quote info in separate tables, 400 tables with 3000
>records each (and growing). For this amount of data it's reasonable to use
>separate tables, but I tried to store all records in one table and it was
>still fast (in mySQL but that wouldnät have worked in mSQL that I started
>out with) and much easier to perform queries involving different shares.
>The important thing is to add indexes for the fields Your are going to look
>up or search. Fields like city, first name and family name should have
>indexes which speed up searching drastically, especially if You require the
>beginning of the name to be given (selects using field like '%substring%'
>is slow whereas field like 'startstring%' is fast).
>  Erik Liljencrantz
>At 11:36 1999-06-23 +0000, Sasha Pachev wrote:
>>Sean Hynes wrote:
>>> Hello,
>>> I am creating a Yellow Page system for many cities. I don't have a lot of
>>> mysql experience so some pointers would be much appreciated.
>>> Lets say there are 500 cities and there will be 100 listings per city.
>>> Is it better to have one table with all entries , searchable by category or
>>> is it better to have a table for each city?
>>I would prefer separate tables. Even if you do not have a lot of data,
>>and can get decent perfomance by putting everying into one table, having
>>to deal with several tables will make you design/code a better scalable
>>application .
>>Sasha Pachev
>> (home)
>> (work)
>Erik Liljencrantz, E-ell-Data,
>erik@stripped, +46 150 250 58, +46 70 51 8 51 26
>Aspenaes, 640 25 JULITA, SWEDEN
>Please check "" before
>posting. To request this thread, e-mail mysql-thread5765@stripped
>To unsubscribe, send a message to the address shown in the
>List-Unsubscribe header of this message. If you cannot see it,
>e-mail mysql-unsubscribe@stripped instead.

Export to text?Robert Pruitt23 Jun
  • Yellow Page SetupSean Hynes23 Jun
    • Re: Yellow Page SetupSasha Pachev23 Jun
      • Re: Yellow Page SetupErik Liljencrantz23 Jun
        • Re: Yellow Page SetupSean Hynes24 Jun
      • Re: Yellow Page SetupSasha Pachev24 Jun
    • Re: Yellow Page SetupBrian Moon24 Jun
Re: Export to text?Kevin Smith23 Jun