Re: "All triggers are evil",..., really?

  • From: "Toon Koppelaars" <toon@xxxxxxxxxxx>
  • To: "Clarke, Andrew" <andrew.clarke@xxxxxxxxxx>
  • Date: Thu, 21 Aug 2008 17:17:55 +0200

All other(*) data constraints in my database design.

*: other = other than the ones that I can deal with declaratively.

EMP-DEPT examples:
- There can be at most one PRESIDENT in EMP table.
- Everybody has less salary than his/her direct manager.
- No department can have more than 30 employees.
- Every department with a MANAGER, should also have an ADMINISTRATOR.
- ...
etc.

On Thu, Aug 21, 2008 at 4:11 PM, Clarke, Andrew <andrew.clarke@xxxxxxxxxx>wrote:

> >>  If all constraint validation is correctly 'tucked away' behind
> triggers, then all
> >>  of your other application code (the 'business logic' code) can be
> devoid of
> >>  constraint validation code
>
> What sort of validation would you want to do which can't be done by
> declarative constraints and which you also wouldn't want to include in the
> "'business logic' code"?
>
> Cheers, APC
>
>
> A P Clarke
> Software Architect
> Logica UK Public Sector Division
> Stephenson House
> 75 Hampstead Road
> London
> UK
> NW1 2PL
> Direct Tel: +44 (0)207 230 3160
> Fax: +44 (0)207 446 1352
> Email: andrew.clarke@xxxxxxxxxx
>
>
> This e-mail and any attachment is for authorised use by the intended
> recipient(s) only. It may contain proprietary material, confidential
> information and/or be subject to legal privilege. It should not be copied,
> disclosed to, retained or used by, any other party. If you are not an
> intended recipient then please promptly delete this e-mail and any
> attachment and all copies and inform the sender. Thank you.
>
>


-- 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Toon Koppelaars
RuleGen BV
+31-615907269
toon_at_rulegen_dot_com
www_dot_rulegen_dot_com

Author: "Applied Mathematics for Database Professionals"

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 08-2008