fenway

If it's still an issue, the post the new output, they expected output, and I'll take a closer look.

http://dev.mysql.com/doc/refman/5.0/en/stored-routines.html

That because you need to group by the YEAR_MONTH as well -- so simply alias that column, and all it to the GROUP BY clause.

I see nothing special about any of those characters. What's more, you MUST escape every string to send to mysql.

No, the problem you're having is with the dates -- because you've turned one column into two. EXTRACT(YEAR_MONTH FROM yourDate).

Link how?

Yes it does, they are usually no longer distinct if you add that column Not Distinct: 1, table1 1, table2 removing what table they came from make them distinct You're missing the point --- MySQL is still running DISTINCT, and wasting it's time. The fact that you might want to know what table they originated from is not the issue.

http://php.net/manual/en/mysqli.insert-id.php

That has absolutely nothing do with with the "missing" rows -- they're missing because they're not distinct. MySQL thinks it's doing you a favour. That will indirectly make them non-distinct -- but that's not robust.

This topic has been moved to PHP Coding Help. http://www.phpfreaks.com/forums/index.php?topic=352952.0

UNION is implicitly UNION DISTINCT. If you don't want that, use UNION ALL.

Instead of grouping by the date parts separately, simply use YEARMONTH(), and then you can format it on output.

This topic has been moved to Application Design. http://www.phpfreaks.com/forums/index.php?topic=352947.0

I'm confused by your design -- and why you're using non-aggregated fields in your SELECT list.

I just noticed your ID is a timestamp? Bad idea. Use a surrogate key -- BIGINT UNSIGNED AUTO_INCREMENT -- as the primary key. Make another column for the timestamp.

There must be dozens of WAMP installation tutorials out there.

I'm confused about your choice of key -- and so is mysql.

DISTINCT will be very slow on large datasets.

This topic has been moved to Application Design. http://www.phpfreaks.com/forums/index.php?topic=352821.0

That means something is wrong, through -- have you tried to run ANALYZE TABLE, and then remove the STRAIGHT_JOIN?

Sorry, switch the order of the tables.

What's giving you these errors?

Why is this even an SP?

Not sure why mysql wants to scan tariff table first.... seems wrong. Try using STRAIGHT_JOIN.

Yeah, wordpress has no idea how to write proper mysql queries.