Re: validation

"Knut Talman" <knut.talman_at_mytoys.de> wrote in message news:3CE38F44.4DE1CB2D_at_mytoys.de...
> Nuno Souto wrote:
>
> > Often the separation line is hazy. Particularly when dealing with
J2EE
> > designers: for them everything has to be "decoupled" from anything
that
> > is not Java. And "coupled" with EJBeans. Bottom line: they
simply shift
> > the maintenance needs around and make them totally coupled to the
app
> > server. A total mistake, for which we have to thank Sun and their
> > "illuminated" designers...
>
> And what about referential integrity? As I said earlier, some apps
even don't
> use database mechanisms to ensure referential integrity.
> Me, myself and I always always use it. Even w/o the application I
have a way to
> ensure or check referential integrity.

I believe that this is critical. The 'closer' you can keep the RI and business rules in the DB, the better you're off. Otherwise what happens when application Y comes along developed by yet another group? As Niall points out, to ensure an optimal user experiece, it's important to copy some of these checks to the front-end. This minimizes the chatter between the front-end and the back-end.

--
Pablo Sanchez, High-Performance Database Engineering
mailto:pablo_at_hpdbe.com
http://www.hpdbe.com
Available for short-term and long-term contracts