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

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

Ovid
  (email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Wednesday June 16, 2004
01:31 PM

Database Programming Rule #1

[ #19305 ]

In production code, if your SELECT statement returns more than one record and it doesn't have an ORDER BY clause, it's probably a bug.

I'm still amazed at the number of professional programmers who don't seem to realize this.

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.
  • I don't follow the logic of requiring an ORDER BY, especially if I'm just slapping some data into a spreadsheet which the PHB's can sort on their own with Excel.

    And what about the performance hit? I find that if I really need ordered data it's often better to just let Perl handle it on the client side.

    What am I missing?

    • ...if I'm just slapping some data into a spreadsheet which the PHB's can sort on their own with Excel.

      For one particular project I was specifically asked *not* to sort the data prior to dumping it into Excel for that very reason.

      PHBs love to sort their spreadsheets :-)
  • I think what you really want to say is "if your program implicitly depends on the order of rows without explicitly using an ORDER BY clause, it's definitely a bug."

    I rarely use ORDER BY -- except when I need it. The trick is to know the difference.

  • I have almost the opposite view.

    When I get involved, it is because the problem requires data munging that the db schema doesn't make easy.

    The data gets aggregated, munched, crunched and gyrated thru so many hoops... that it makes no sense to sort until the data is being output.

    No need to tax the db for that, not when the delivery order (from the db) is not significant.

    On the other hand... yeah, simple grab and display type of things... should have some order imposed upon them.

    And, my final results alwa
  • Not sure I agree with you. It *might* be a bug depending on what you're doing or expecting. Then again, it might not.

    Today I added some code to retrieve email addresses from a table. The order in which the rows are returned to me is irrelevant. I'm not using the data to display on a report or on a webpage, I'm just sending out emails.

    So, does my code have a bug? Maybe, but I'm pretty sure it's got nothing to do with the fact that I didn't use an ORDER BY :-)