Preventing SQL Injection with Prepared Statements

Use named or positional placeholders for user-supplied query values, never interpolate those values into SQL.

The objective is to understand the behavior and operational limits, not only the method name.

What It Does

Use named or positional placeholders for user-supplied query values, never interpolate those values into SQL.

Prerequisites

Use a dedicated development environment and sample data. Where a snippet uses an injected connection, repository, request value or mailer, supply it from your own application setup.

Example 1: Basic Use

A focused working pattern for this topic. Names such as $pdo, $authContext and $repo represent dependencies provided by the application unless initialized in the snippet.

<?php
$stmt = $pdo->prepare('SELECT id FROM invoices WHERE customer_id = ? AND paid = ?');
$stmt->execute([$customerId, 0]);
$unpaid = $stmt->fetchAll(PDO::FETCH_COLUMN);

Example 2: A Second Scenario

A second use case that adds a different operation or data flow specific to this topic.

<?php
$id = filter_input(INPUT_GET, 'id', FILTER_VALIDATE_INT);
if ($id === false || $id === null) { http_response_code(400); exit; }
$stmt = $pdo->prepare('SELECT title FROM posts WHERE id = ?');
$stmt->execute([$id]);

Example 3: Practical Checks

A practical validation, failure or deployment concern specific to this topic.

<?php
$stmt = $pdo->prepare('UPDATE products SET price = :price WHERE id = :id');
$stmt->bindValue(':price', 199, PDO::PARAM_INT);
$stmt->bindValue(':id', 18, PDO::PARAM_INT);
$stmt->execute();

Important Behavior and Edge Cases

Prepared statements do not validate business rules or make untrusted identifiers safe.

For production use, also account for error handling, data validation, resource limits and environment-specific driver behavior.

Comparison with Related Approaches

Common Beginner Mistakes

Key Takeaways

• Use named or positional placeholders for user-supplied query values, never interpolate those values into SQL.
• Prepared statements do not validate business rules or make untrusted identifiers safe.
• Use this workflow as a focused starting point rather than a substitute for application-level tests.

Choose this API or pattern when its exact semantics match your task, and verify the result against the database driver and runtime used by your application.