• Nadrek (10/1/2009)


    jcrawf02 (10/1/2009)


    Why would you want the db to do this? Why wouldn't you require the application to..[clipped]..the app takes care of the rest.

    Philosophically, with this argument, why do you want the DB to have _any_ constraints at all?

    Because I assume there are multiple apps, at least one is flawed, and at least some rows will sooner or later be entered another way.

    Hardly saying that, but you're arguing that the db needs to be perfect where the app is not, versus the reverse. Since the goal of the app should be to reduce the work the user has to perform to accomplish the task, it should already be doing this.

    ---------------------------------------------------------
    How best to post your question[/url]
    How to post performance problems[/url]
    Tally Table:What it is and how it replaces a loop[/url]

    "stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."