Re: Data Constraints AND Application Constraints

From: David Cressey <david.cressey_at_earthlink.net>
Date: Thu, 17 Mar 2005 18:43:22 GMT
Message-ID: <edk_d.6894$qW.5928@newsread3.news.atl.earthlink.net>

"Paul" <paulsnewsgroups_at_hotmail.com> wrote in message news:19aj3153u9hl2g8uja0jj3jkpb5iea0ggv_at_4ax.com...
>
>
> "David Cressey" <david.cressey_at_earthlink.net> wrote:
>
>
> >Absolutely, yes. Let's say that a certain field in a data entry form has
to
> >have a number in the range 20,000 to 99,000, and may not be left blank.
>
>
> > The DBMS can better use its
> > resources if it doesn't get distracted by this stuff.
>
>
> But surely for a rule like the one above, you would also implement a
> constraint in the db?
>

Well... yes I would. But my argument about the DBMS better using it's resources stands.
If it's implemented in both places, the DBMS will still experience less traffic, because it won't
see the bad transactions that get snagged by the application. Received on Thu Mar 17 2005 - 12:43:22 CST