Databases
StackOverflow2013
Postsdbo
POmysql query inner join slowing
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POmysql query inner join slowing
    primarykey
    data
    text
    <p>I have the following database structure:</p> <pre><code>CREATE TABLE IF NOT EXISTS `business` ( `id` bigint(20) NOT NULL AUTO_INCREMENT, `address` varchar(255) NOT NULL, `city` varchar(255) NOT NULL, `state` varchar(255) NOT NULL, `postal` int(11) NOT NULL, `country` varchar(255) NOT NULL, `lat` float NOT NULL, `lng` float NOT NULL, `name` varchar(255) NOT NULL, `phone` varchar(255) NOT NULL, `email` varchar(255) NOT NULL, `website` varchar(255) NOT NULL, `userID` bigint(20) NOT NULL, `url` varchar(255) NOT NULL, `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, `clicks` bigint(20) NOT NULL, `oHours` varchar(255) NOT NULL, `featured` tinyint(1) NOT NULL, `imageThumb` varchar(255) NOT NULL DEFAULT 'default.jpg', `imageOrig` varchar(255) NOT NULL DEFAULT 'default.jpg', `flag` tinyint(1) NOT NULL, `display` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=589846 ; </code></pre> <p>This table (business) has 507,736 records</p> <pre><code>CREATE TABLE IF NOT EXISTS `businesscat` ( `id` bigint(20) NOT NULL AUTO_INCREMENT, `bizID` bigint(20) NOT NULL, `catID` bigint(20) NOT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=589863 ; </code></pre> <p>This table (businesscat) has 519,825 records</p> <pre><code>CREATE TABLE IF NOT EXISTS `category` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(255) NOT NULL, `url` varchar(255) NOT NULL, `icon` varchar(255) NOT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=7 ; </code></pre> <p>This table (category) has only 5 records</p> <p>So, my problem is I'm trying to get 100 records with calculation of nearest business using the ff:</p> <pre><code>SELECT business.name , business.lng , business.lat , business.address , business.city , business.state , business.postal , business.phone , business.url , business.imageThumb , businesscat.catID , category.icon , (((acos(sin((".$lat."*pi()/180)) * sin((business.lat*pi()/180)) + cos((".$lat."*pi()/180)) * cos((business.lat*pi()/180)) * cos(((".$lng."-business.lng)*pi()/180)))) * 180/pi())*60*1.1515) AS distance FROM business INNER JOIN businesscat ON businesscat.bizID=business.id INNER JOIN category ON category.id=businesscat.catID ORDER BY distance LIMIT 100 </code></pre> <p>Any idea to make it faster? </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USrene
    1. USMar Cejas
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POmysql query inner join slowing
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI assume all runs fine if you leave out the Order by distance?
      singulars
      1. POmysql query inner join slowing
      1. USrene
    2. COHave you defined indexes for businesscat.bizID and businesscat.catID? Also, you might be able to optimize your businesscat table by dropping the id and declaring bizID and catID as the primary key, though I doubt that this will improve your query.
      singulars
      1. POmysql query inner join slowing
      1. USMike Nakis
    3. CO"Faster" than what?
      singulars
      1. POmysql query inner join slowing
      1. USLightness Races in Orbit
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload