Re: Check constraints, the impossible dream?

I think it's the sort of strategy I would agree with.

However, one option that I have suggested a couple of times as a variant is to have the client load the constraints from the database then apply them locally. The code framework is non-trivial, and you have to be very strict in enforcing coding conventions, but you guarantee that the database and the client have exactly matching checks.

--
Jonathan Lewis
http://www.jlcomp.demon.co.uk

Next Seminar - UK, April 3rd - 5th
http://www.jlcomp.demon.co.uk/seminar.html

Host to The Co-Operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html

Author of:
Practical Oracle 8i: Building Efficient Databases


Paul Brewer wrote in message
<3c9ba9da_3_at_mk-nntp-1.news.uk.worldonline.com>...


>

>My colleagues and I had a dilemma over this when we went over to Oracle in

>1995.

>Our conclusion was that under most circumstances, the optimum solution for

>an OLTP app is to validate twice over; catch it in the client with a

>meaningful message for the user, *and* have the db as a sort of

>wicketkeeper.

>Someone wrote 'keep the application honest'; as a DBA that seems a

>reasonable approach.

>What do you think?

>

>Paul

>