Whether 1-tier, 2-tier, n-tier, the DBMS is the final judge of what gets in.
In real world experience, I find it useful to edit the data on the front-end
(guessing at what the DBMS will accept or reject) and then try to send
useful data to the database. It is then up to the DBMS to accept or reject.
Best case for all, but junk still gets in
"Arthur Yeo" <ayeo_at_acm.org> wrote in message
news:I73p9.29456$7I6.92391_at_rwcrnsc52.ops.asp.att.net...
> Theoretically, everyone knows that business logic is supposed to be in the
> middle-tier according to the 3-tier architecture. This seems to be
> counter-intuitive to Active Database concepts such as putting business
logic
> in triggers with help from store procedures in the DBMS (which are all in
> the 3rd-tier of the 3-tier architecture.)
>
> Question: do you guys know of any guidelines (or may be even stds)
proposed
> to decide when certain business logic is better put in the backend (DB
> triggers/stored procedures)?
>
> Cheers,
> Arthur
>