note 123662 added to security.database.design

> 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. ---- Server IP: 208.43.231.9 Probable Submitter: 185.85.3.142 (proxied: 178.219.30.155) ---- Manual Page -- http://php.net/manual/en/security.database.design.php Edit -- https://master.php.net/note/edit/123662 Del: integrated -- https://master.php.net/note/delete/123662/integrated Del: useless -- https://master.php.net/note/delete/123662/useless Del: bad code -- https://master.php.net/note/delete/123662/bad+code Del: spam -- https://master.php.net/note/delete/123662/spam Del: non-english -- https://master.php.net/note/delete/123662/non-english Del: in docs -- https://master.php.net/note/delete/123662/in+docs Del: other reasons-- https://master.php.net/note/delete/123662 Reject -- https://master.php.net/note/reject/123662 Search -- https://master.php.net/manage/user-notes.php