| List: | General Discussion | « Previous MessageNext Message » | |
| From: | <sinisa | Date: | October 8 1999 1:13pm |
| Subject: | Re: Query optimizing | ||
| View as plain text | |||
Manik Surtani writes: > Hi, > > Can anyone tell me which of the 2 following ways > to extract data are faster/more efficient? > > 1. Method 1 > ********** > > SELECT NAME, CODE FROM PRODUCT LIMIT 0, 25; > > ... Start Loop: for each row obtained above, > > SELECT SUM(VALUE) FROM PRIPROD WHERE > CODE='code_obtained_above'; > > ... End Loop > > > 2. Method 2 > ********** > > SELECT > PRODUCT.CODE, > PRODUCT.NAME, > SUM(PRIPROD.VALUE) > FROM > PRODUCT, > PRIPROD > WHERE > PRODUCT.CODE=PRIPROD.CODE > GROUP BY > PRODUCT.CODE > LIMIT 0, 25; > > > > The reason I ask is because both PRODUCT and > PRIPROD tables have in excess of 1 million rows, > and this query needs to be very efficient. If > there is a still better way to do this (using > joins, whatever) pls let me know ..... > > Thanks in advance, > > > -- > Manik Surtani > Chief Technology Officer > Espada (Pvt.) Ltd. > http://www.espadanet.com > ICQ: 853533 > > * The best in e-commerce solutions * > > Seconde one. Definitely. Sinisa +----------------------------------------------------------------------+ | TcX ____ __ _____ _____ ___ == mysql@stripped | | /*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic | | /*/ /*/ /*/ \*\_ |*| |*||*| mailto:sinisa@stripped| | /*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaka, Cyprus | | /*/ /*/ /*/\*\_/*/ \*\_/*/ |*|____ | | ^^^^^^^^^^^^/*/^^^^^^^^^^^\*\^^^^^^^^^^^ | | /*/ \*\ Developers Team | +----------------------------------------------------------------------+
| Thread | ||
|---|---|---|
| • Query optimizing | Manik Surtani | 8 Oct |
| • Re: Query optimizing | sinisa | 8 Oct |
| • Re: Query optimizing | Bob Kline | 8 Oct |
| • Re: Query optimizing | sinisa | 8 Oct |
| • Re: Query optimizing | Bob Kline | 8 Oct |
| • Re: Query optimizing | Bob Kline | 8 Oct |
| • RE: Query optimizing | bkline | 9 Oct |
| • RE: Query optimizing | sinisa | 9 Oct |
| • RE: Query optimizing | Bob Kline | 9 Oct |
| • Re: Query optimizing | Tonu Samuel | 10 Oct |
| • Re: Query optimizing | Bob Kline | 10 Oct |
| • RE: Query optimizing | Leif Neland | 10 Oct |
| • RE: Query optimizing | sinisa | 10 Oct |
| • RE: Query optimizing | Bob Kline | 10 Oct |
| • RE: Query optimizing | Bob Kline | 10 Oct |
| • RE: Query optimizing | bkline | 10 Oct |
| • RE: Query optimizing | sinisa | 11 Oct |
| • RE: Query optimizing | Bob Kline | 11 Oct |
| • RE: Query optimizing | Patrick Greenwell | 10 Oct |
| • RE: Query optimizing | sinisa | 11 Oct |
| • RE: Query optimizing | Bob Kline | 11 Oct |
| • RE: Query optimizing | Michael Widenius | 11 Oct |
| • RE: Query optimizing | Bob Kline | 11 Oct |
| • RE: Query optimizing | Bob Kline | 11 Oct |
| • RE: Query optimizing | Bob Kline | 11 Oct |
| • Re: Query optimizing | Michael Widenius | 11 Oct |
| • Re: Query optimizing | Michael Widenius | 11 Oct |
| • RE: Query optimizing | lindberg | 10 Oct |
| • RE: Query optimizing | Bob Kline | 10 Oct |
| • RE: Query optimizing | Michael Widenius | 11 Oct |
| • RE: Query optimizing | Michael Widenius | 11 Oct |
| • Re: Query optimizing | Renato Lins | 10 Oct |
| • Re: Query optimizing | Tonu Samuel | 10 Oct |
