MySQL Lists are EOL. Please join:

List:General Discussion« Previous MessageNext Message »
From:Richard Unger Date:September 17 2002 8:49pm
Subject:FW: aggregate functions producing bad data
View as plain text  
MySQL <-- to defeat the spam filter

-----Original Message-----
From: Richard Unger 
Sent: Tuesday, September 17, 2002 1:46 PM
To: 'Dan Nelson'
Cc: mysql@stripped
Subject: RE: aggregate functions producing bad data


Thanks, I figured it out.  It turns out there were some calls for which call_end IS NULL. 
I had originally eliminated that possiblity because I mistakenly checked if call_end =
NULL (instead of IS).

Thanks for pointing me in the right direction.

Cheers,
Rich

> -----Original Message-----
> From: Dan Nelson [mailto:dnelson@stripped]
> Sent: Tuesday, September 17, 2002 1:13 PM
> To: Richard Unger
> Cc: mysql@stripped
> Subject: Re: aggregate functions producing bad data
> 
> 
> In the last episode (Sep 17), Richard Unger said:
> > From: Dan Nelson [mailto:dnelson@stripped]
> > > In the last episode (Sep 17), Brian Reichert said:
> > > > One thing I'd check:  what happens if 
> t_calllog_calls.id is NULL?
> > > 
> > > Also check if call_end or call_start are NULL; that will 
> > > cause both IFs
> > > to fail.  Don't you love NULLs :)
> > 
> > Ooh, good suggestion.  I hadn't thought of that!
> > 
> > ...but no, none of the call_start or call_end fields are NULL.
> 
> Next step is to do a "REPAIR TABLE t_calllog_calls", in case 
> your index
> got damaged at some point.  The next step after that is to make a copy
> of your table, and remove records one by one until your total works,
> then find out what's special about the last record you removed.
> 
> -- 
> 	Dan Nelson
> 	dnelson@stripped
> 
Thread
FW: aggregate functions producing bad dataRichard Unger18 Sep