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.
  • Machine communication is not human communication.

    SQL is not about reducing redundancy.

    SQL is about offloading work related to data storage retrieval to a dedicated machine.

    Should I have to implement my own grouping code in every single application?
    • Should I have to implement my own grouping code in every single application?

      No, I think his basic idea is that the database should be able to deduce the GROUP BY clause from the rest of the statement. Now, a database complains if you output a column that isn't in an aggregate function, or in the GROUP BY clause. Instead, it could implicitly add the column to the GROUP BY clause.

      I don't think that overall it would save much typing. And having to be explicit has its advantages, in cases the SQL statement implies a different grouping than what you had in mind.