• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 93
  • Last Modified:

Mysql GROUP BY, how to detect when new "group"?

Hi,

When using "SELECT * FROM table GROUP BY city"

What is the best method to detect a new group/city?
I need to post a new html-table and list all related database records associated to each city.

Any suggestions?
0
kgp43
Asked:
kgp43
  • 2
1 Solution
 
Chris StanyonCommented:
Your SQL won't do what you think it will - it will simply return one record for each City - because you're grouping your records by City. The rest of the data shown for a record is likely to be from the first record in that City's group.

You may be better off writing your App to select the Distinct Cities, and then loop through that list, firing off another query to select records that match that city.
0
 
kgp43Author Commented:
You're right.
Think i'm going to use ORDER BY and then check if new city is different from previous one, if so: post table start and ending.

Think that will work?
0
 
Chris StanyonCommented:
It will, but it doesn't feel like a clean way of doing it. Any reason to not do it the way I suggested. It's actually pretty easy. Here's a very quick demo using PDO:

<?php
$stmt = $dbh->prepare("SELECT * FROM table WHERE city = ?");

foreach ($dbh->query("SELECT DISTINCT city FROM table;") as $row):
	printf("<h1>City: %s</h1>", $row->city);
	
	echo "<table>";
	
	$stmt->execute( array($row->city) );
	while ($row = $stmt->fetch()):
		printf("<tr><td>%s</td><td>%s</td></tr>", $row->column1, $row->column2);
	endwhile;
	
	echo "</table>";
	
endforeach;
?>

Open in new window


Basically it selects a distinct list of cities, and loops through them. For each city it finds it pulls the matching records from your database, and displays a table containing the data.
0
 
PortletPaulfreelancerCommented:
"SELECT * FROM table GROUP BY city" is bad for 2 reasons (at least)

1. that * will produce changes that your downstream code may not be prepared for, it is a bug creator 'par excellence'

2. MySQL has this bizarre "feature" that allows this lazy syntax, and it "approximates" values for the fields (read: guesses)

In most flavours of SQL you MUST specify ALL the fields that will form a group, then ALL OTHER fields must be handled by an aggregate function like MAX() MIN() SUM() COUNT() etc.

The default settings of MySQL ignore this convention; and don't require the more stringent syntax. One risk is (if someone does alter the settings) and the system all of a sudden will require precise syntax and all previous lazy syntax grouping queries will fail. The other, perhaps more disturbing, risk is that the data in all the non-aggregated columns just isn't accurate and should be relied upon (unless you do enjoy "indeterminate" results).

MySQL extends the use of GROUP BY so that the select list can refer to nonaggregated columns not named in the GROUP BY clause. This means that the preceding query is legal in MySQL. You can use this feature to get better performance by avoiding unnecessary column sorting and grouping. However, this is useful primarily when all values in each nonaggregated column not named in the GROUP BY are the same for each group. The server is free to choose any value from each group, so unless they are the same, the values chosen are indeterminate.
http://dev.mysql.com/doc/refman/5.0/en/group-by-handling.html (emphasis added)

Use these "lazy group bys" with caution IMHO
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now