Quote:
Originally posted by Moskie
A shot in the dark...
isn't the GROUP BY command lumping all the records together that have the same enhancement_id? If that's the case, then all the results are merged into that one record being returned... do you mean to have ORDER BY?
EDIT:
or maybe you need to be more specific on *which* enhancement_id you want to group by?
|
Yeah, I think the GROUP BY usage is definitely a factor in the problem, but I'm not sure how else it could be used, or what it should be replaced with. If I eliminate the GROUP BY clause completely, my query returns, literally, 1500 results -- every possible combination of server/origin/enhancement effect. If I change the enhancement_id to e.enhancement_id or fj or oj, I get the same result as I get with just "GROUP BY enhancement_id". Thanks for the response.
