Post reply

Using the Best

  • September 14, 2009 at 4:28 am

    #1053058

    Well, set operations on a relational database aren't the way to do everything in computing, particularly if you're developing an application for computer operators who are not trained in set-based operations - who probably interact with the database RBAR in their heads instead of batchwise as in the days of punched cards. And if a specification isn't well met by a set-based solution, you can't say that the specification is wrong. There is a growing community of heterodoxist database professionals who spit on the relational database, the object database people for instance, and while their arguments haven't convinced me yet, I respect their right to hold an opinion and recognise that sometimes they may get the job done better... at least until their latest project fails spectacularly and the boring old SQL people step in to save the day. Failure can be good if it's happening to somebody else. 😉

  • September 14, 2009 at 9:22 pm

    #1053544

    rja.carnegie (9/14/2009)

    ... at least until their latest project fails spectacularly and the boring old SQL people step in to save the day. Failure can be good if it's happening to somebody else. 😉

    Heh... Man, do I agree with that. In fact, that's the short version of my job description. :hehe:

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 2 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply