Many of the more mature databases support the concept of prepared
statements. What are they? You can think of them as a kind of compiled
template for the SQL that you want to run, that can be customized using
variable parameters. Prepared statements offer two major benefits:
The query only needs to be parsed (or prepared) once, but can be
executed multiple times with the same or different parameters. When the
query is prepared, the database will analyze, compile and optimize it's
plan for executing the query. For complex queries this process can take
up enough time that it will noticeably slow down your application if you
need to repeat the same query many times with different parameters. By
using a prepared statement you avoid repeating the
analyze/compile/optimize cycle. In short, prepared statements use fewer
resources and thus run faster.
The parameters to prepared statements don't need to be quoted; the
driver handles it for you. If your application exclusively uses
prepared statements, you can be sure that no SQL injection will occur.
(However, if you're still building up other parts of the query based on
untrusted input, you're still at risk).
Prepared statements are so useful that they are the only feature that PDO
will emulate for drivers that don't support them. This ensures that you
will be able to use the same data access paradigm regardless of the
capabilities of the database.
Example #1 Repeated inserts using prepared statements
This example performs an INSERT query by substituting a name
and a value for the named placeholders.
// insert another row with different values $name = 'two'; $value = 2; $stmt->execute(); ?>
Example #3 Fetching data using prepared statements
This example fetches data based on a key value supplied by a form.
The user input is automatically quoted, so there is no risk of a
SQL injection attack.
<?php $stmt = $dbh->prepare("SELECT * FROM REGISTRY where name = ?"); if ($stmt->execute(array($_GET['name']))) { while ($row = $stmt->fetch()) { print_r($row); } } ?>
If the database driver supports it, you may also bind parameters for
output as well as input. Output parameters are typically used to retrieve
values from stored procedures. Output parameters are slightly more complex
to use than input parameters, in that you must know how large a given
parameter might be when you bind it. If the value turns out to be larger
than the size you suggested, an error is raised.
Example #4 Calling a stored procedure with an output parameter
You may also specify parameters that hold values both input and output;
the syntax is similar to output parameters. In this next example, the
string 'hello' is passed into the stored procedure, and when it returns,
hello is replaced with the return value of the procedure.
Example #5 Calling a stored procedure with an input/output parameter
<?php $stmt = $dbh->prepare("SELECT * FROM REGISTRY where name LIKE '%?%'"); $stmt->execute(array($_GET['name']));
// placeholder must be used in the place of the whole value $stmt = $dbh->prepare("SELECT * FROM REGISTRY where name LIKE ?"); $stmt->execute(array("%$_GET[name]%")); ?>