Hi Benjamin,
Sorry for the late reply and not giving you any more replies..
Was away some days...
Thanks for all the help on my query question..
Indeed like you said, the query now probably is as fast as he will ever get...
And that is fast indeed, there isn't any waiting period anymore...
I al
Hi Benjamin...
> > database almost 2 years ago... But the orderid I can convert without
> > a problem to an INT because all data only are numbers... :-(
> It's not so important, that orderid is not of type VARCHAR (although
> better), but more important, as I said, that co.id and cpo.orderid are
Hi.
On Mon, Jul 23, 2001 at 02:33:21PM +0200, [EMAIL PROTECTED] wrote:
> Hi Benjamin...
>
> I am not sure, but it looks that I (sometimes) get an email back
> telling me that your email address isn't working..
> >recipient [EMAIL PROTECTED] does not exist, verify e-mail address, please
Hm. But
Hi Benjamin...
I am not sure, but it looks that I (sometimes) get an email back telling me that your
email address isn't working..
>recipient [EMAIL PROTECTED] does not exist, verify e-mail address, please
I still want to reply on you other mail, but your email just showed me something
awful!
Hi.
On Sun, Jul 22, 2001 at 03:38:10AM +0200, [EMAIL PROTECTED] wrote:
> Hi Benjamin,
>
> Just a quick gif picture of the explain of the other query I made..
> (It's quite late now and I will read your email tomorrow again..)
>
> > Could you post an EXPLAIN for it? I am curious to see it.
> >
ALL PRIMARY,id2596 where used
Edit Delete cpo ALL 4431 where used
Bye Bye
David
- Original Message -
From: "Benjamin Pflugmann" <[EMAIL PROTECTED]>
To: "David Bouw" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]&g
Hi Don.
On Sat, Jul 21, 2001 at 03:28:45PM -0500, [EMAIL PROTECTED] wrote:
[...]
> > There is one exception, though, there are compound keys, which will be
> > of use. So,
> >
> > INDEX(id), INDEX(id)
> >
> > makes no sense, but
> >
> > IDNEX(id), INDEX(id,ordernr)
> >
> > may make sense.
On 21-Jul-2001 Benjamin Pflugmann wrote:
> Hi David!
>
>
> Filesize and insertion/update speed are the main reasons. Another is
> to only use what you really need, i.e. creating indexes which you are
> not sure about using at all, should be avoided.
>
>> I use PHPmyAdmin a lot to place inde
Hi David!
On Sat, Jul 21, 2001 at 04:08:51PM +0200, [EMAIL PROTECTED] wrote:
[...]
> > SELECT * FROM orders, productorders WHERE productorders.orderid = orders.id
> > SELECT * FROM orders JOIN productorders WHERE productorders.orderid = orders.id
>
> Yes, I see, this is basically the apples/pear
Hi Benjamin
> > Then I got my hands on examples which used a left join examples.. I
> > have never tried a normal join (sigh..), but thinking of it, what is
> > the difference between an left join and a normal join..??
> With a "normal join" (I don't know the technical term), I mean
> something l
Hi.
On Fri, Jul 20, 2001 at 11:22:56PM +0200, [EMAIL PROTECTED] wrote:
>
> > SELECTbrand.brandname,
> > SUM((productorders.quantity)*(productorders.price)) AS turnover
> > FROM orders
> > LEFT JOIN productorders ON productorders.orderid = orders.id
> > LEFT JOI
_brand
Table Non_unique Key_name Seq_in_index Column_name Collation Cardinality Sub_part
perfect_brand 0 PRIMARY 1 id A 16
I am also going to do some reading myself on the normal join, thanks for your info...
Bye Bye
David
- Original Message -
From: "Benjamin Pflugmann"
> I added comments and a recipe to my debug function collection.
> You can download at the address
> http://pferdezeitung.de/php3/toosDebug.zip
Sorry - in adding comments I inadvertently dropped several lines
in function debugMsg. So if you downloaded version 0.4, please
fetch version 0.
Hello.
[...]
> Here is the query
>
[query reformatted... btw, it would have been nice if you had done this at first]
SELECTbrand.brandname,
SUM((productorders.quantity)*(productorders.price)) AS turnover
FROM orders
LEFT JOIN productorders ON productorders.orderid =
I added comments and a recipe to my debug function collection.
You can download at the address
http://pferdezeitung.de/php3/toosDebug.zip
> Well, I don't know about David, but I'd be very interested in your
> stopwatch program
table, sql
--
Herzlich
Werner Stuerenburg
I'm by no means an expert, but I made left joins with 2 tables
with about 4500 and 2800 records each. They were basically
structured quite the same. I had response time at about .7
seconds on the larger and and 15 seconds on the other - which
kept me wondering why that should be.
I found that the
Hi there,
I am wondering if the Left Join syntax is a very inefficient query for MySQL (and
other databases generally speaking..)???
I have a table which consits of a few tables from which the bigest table contains
about 4500 records...
Heres the scenario:
I have 5 tables fom an ecommerce s
17 matches
Mail list logo
