• sherifffruitfly (5/8/2012)


    As for the pissing match - meh. There's times to use stuff and times not to. Never been a fan of the religious fanatics on either the ALWAYSUSEIT and NEVERUSEIT sides. Both sides seem to me to substitute easy-to-remember rules in place of actually thinking about the needs of the current task.

    -sff

    You're totally out of line. There's no pissing match when something gets its butt kicked 45 to 1. You don't need to use inflamatory terms like "religious fanatics" when good people have found an extreme performance problem. And if you're so proud of Expresso, you might want to provide a couple of your own performance tests.

    --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)