note 77120 added to security.database
| From: | DaveMartin at osu1 dot php dot net | Date: | Thu, 16 Aug 2007 07:15:01 +0000 |
| Subject: | note 77120 added to security.database | ||
| Groups: | php.notes | ||
| Request: | Send a blank email to php-notes+get-129514@lists.php.net to get a copy of this message | ||
The posting below is at the very best extremely POV.
There is no more reason to assume you would want to change database vendor than there is to assume
you might want to port your php code to Java for example. In either case, its going to be a matter
of luck where your business rules sit.
Even if your business rules sit in your application, SQL is NOT portable. Oracle outer joins and
pivot queries for example, can look completely different to those in other vendors software
(particularly from 8i or lower). This fact alone means that changing your DB vendor requires work on
your business rules either in the database or in the application.
Having your rules in the database and keeping the sql in application simple, will at least keep the
work in the database if you need to change DB vendor. If you have the rules in the PHP, you'll
have to change both.
----
Server IP: 69.147.83.197
Probable Submitter: 83.80.16.62
----
Manual Page -- http://www.php.net/manual/en/security.database.php
Edit -- https://master.php.net/note/edit/77120
Del: integrated -- https://master.php.net/note/delete/77120/integrated
Del: useless -- https://master.php.net/note/delete/77120/useless
Del: bad code -- https://master.php.net/note/delete/77120/bad+code
Del: spam -- https://master.php.net/note/delete/77120/spam
Del: non-english -- https://master.php.net/note/delete/77120/non-english
Del: in docs -- https://master.php.net/note/delete/77120/in+docs
Del: other reasons-- https://master.php.net/note/delete/77120
Reject -- https://master.php.net/note/reject/77120
Search -- https://master.php.net/manage/user-notes.php