jcrawf02 (10/1/2009)
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.
I'm a DBA, so yes, the db must be perfect. 😀 Also we may have multiple applications accessing a single database so I don't want to rely on the application logic. Also, the application should reduce the work a user has to perform, but this is completely different from accurately modeling the data. Part of data modeling in this case is the ability to store interval or ranged data (dates or numbers) that do not overlap.