note 101463 added to security.database.sql-injection

Another suggestion would be to build a series of DB procedures / functions that you give the DB user access to to manipulate or select data. That way, all input would run through this exposed interface and all parameters are forced to be typecast (or rejected). ---- Server IP: 208.69.120.55 Probable Submitter: 69.174.169.69 ---- Manual Page -- http://www.php.net/manual/en/security.database.sql-injection.php Edit -- https://master.php.net/note/edit/101463 Del: integrated -- https://master.php.net/note/delete/101463/integrated Del: useless -- https://master.php.net/note/delete/101463/useless Del: bad code -- https://master.php.net/note/delete/101463/bad+code Del: spam -- https://master.php.net/note/delete/101463/spam Del: non-english -- https://master.php.net/note/delete/101463/non-english Del: in docs -- https://master.php.net/note/delete/101463/in+docs Del: other reasons-- https://master.php.net/note/delete/101463 Reject -- https://master.php.net/note/reject/101463 Search -- https://master.php.net/manage/user-notes.php