--- In firebird-support@yahoogroups.com, "Ann W. Harrison":

> [...] But the flexibility of triggers
> and stored procedures is quite a challenge to emulate in any
> declarative language, so I think we'll have procedures and triggers
> for a while.
>

I remember a well-paid, high positioned analyst at
a not insignificant company, who praised the RDBMS part
of the framework whose development he supervised, to
- not let any client have access to any table
- all work done through stored procedures

I saw this religion in some Microsoft SQL material, too.

I didn't found the idea that bad, when first heard about. And now I'm
still ambivalent.

The idea, besides some ominous 'security', is loose coupling of client
code and table structure.

If you change/upgrade your table structure for new needs, old clients
still see the same old interface via SPs.

The counter-argument obviously is, that this theory will become rather
theoretical when non-trivial changes to table structure are required.

Best Regards,
Peter Jacobi