note 123662 deleted from security.database.design by cmb
| From: | cmb@php.net | Date: | Mon, 11 Mar 2019 12:26:03 +0000 |
| Subject: | note 123662 deleted from security.database.design by cmb | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-210350@lists.php.net to get a copy of this message | ||
Note Submitter: o at olgierd dot me
----
> You are encouraged not to implement all the business logic in the web application (i.e. your
> script), instead do it in the database schema using views, triggers or rules. If the system evolves,
> new ports will be intended to open to the database, and you have to re-implement the logic in each
> separate database client. Over and above, triggers can be used to transparently and automatically
> handle fields, which often provides insight when debugging problems with your application or tracing
> back transactions.
This is exactly the other way around. SQL code is difficult to debug, it lacks common programming
language features and is more cumbersome to write and to deploy. You definitely should not implement
your business logic in a Query Language, regardless of how Structured it is.