Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • It surprised me when I saw that Sybase accepted a similar syntax. But the result seemed next to useless. Non-aggregate columns not in the "group by" clause result in a cartesian join, so, every row in the conceptbindings table (via the rtype column) will join with every combination of conceptid and count. I'm not sure if MySQL behaves the same or differently.
    • MySQL returns "some value", maybe the first, for each row of grouped concept. But yes, I'd rather prefer a cartesian product than this unexpected behaviour, even if I can understand why it's like that...
      • Oh no you don't. Not after you've screwed up and accidentally done a cartesian product between 100,000 records and 100,000 records again.

        I loathed that.

        If they want to save me time, just make the GROUP BY clause optional. Because 99% of the time my GROUP BY clause is just going to be all of the non-aggregate functions in my SELECT clause. And I hate having to type in all of that duplicate information.