On Thu, 4 Nov 2010 08:07:02 -0300
Paul Halliday paul.halli...@gmail.com wrote:
SELECT COUNT(signature) AS count, MAX(timestamp) AS maxTime,
INET_NTOA(src_ip), src.cc, INET_NTOA(dst_ip), dst.cc FROM event LEFT
JOIN mappings AS src ON event.src_ip = src.ip LEFT JOIN mappings AS
dst ON
Presumably those records were absorbed into your 'group by' clause, since
there was an entry, from a later time, which had the same values for all the
group by fields.
--
Simcha Younger sim...@syounger.com
Geez, how obvious. I was thinking on a completely different plane. I
feel pretty
Kevin,
Tuesday, November 05, 2002, 12:55:41 PM, you wrote:
KD I've shrunk the dataset down as far as I can to continue to reproduce this
KD issue, but the .gz file is still 1.3MB
KD Running this on 4.0.3 produces the correct results. 4.0.4 doesn't.
KD fetch http://www.dragondata.com/ditsy.gz
I've shrunk the dataset down as far as I can to continue to reproduce this
issue, but the .gz file is still 1.3MB
Running this on 4.0.3 produces the correct results. 4.0.4 doesn't.
fetch http://www.dragondata.com/ditsy.gz
bash-2.05b# mysql test ditsy
bash-2.05b# mysql test
mysql SELECT
toasty,
Sunday, October 27, 2002, 11:17:53 PM, you wrote:
taddc Under some pretty specific conditions, adding a LIMIT clause to a query
taddc will cause incorrect results.
taddc How-To-Repeat:
taddc This bug is NOT present in 4.0.3.
taddc CREATE TABLE `history` (
taddc `id_pic` int(11)
|
++++---+---++-+---+
snip
847 rows in set (0.72 sec)
Fix:
Submitter-Id:
Originator:Kevin Day
Organization:
Stile Project
MySQL support: none
Synopsis: LEFT JOIN selects with ORDER BY and WHERE and LIMIT missing results
Severity