Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Protection from SQL injection


  • From: PFC <lists(at)peufeu(dot)com>
  • To: "Brendan Jurd" <direvus(at)gmail(dot)com>
  • Cc: "Thomas Mueller" <thomas(dot)tom(dot)mueller(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: Protection from SQL injection
  • Date: Tue, 29 Apr 2008 09:26:24 +0200
  • Message-id: <op(dot)uac2yav2cigqcu(at)apollo13(dot)peufeu(dot)com>

On Tue, 29 Apr 2008 01:03:33 +0200, Brendan Jurd <direvus(at)gmail(dot)com> wrote:

On Tue, Apr 29, 2008 at 7:00 AM, PFC <lists(at)peufeu(dot)com> wrote:
I have found that the little bit of code posted afterwards did eliminate SQL holes in my PHP applications with zero developer pain, actually it is
MORE convenient to use than randomly pasting strings into queries.

 You just call
 db_query( "SELECT * FROM table WHERE column1=%s AND column2=%s", array(
$var1, $var2 ));


Implementing this for yourself is crazy; PHP's Postgres extension
already does this for you since 5.1.0:

$result = pg_query_params("SELECT foo FROM bar WHERE baz = $1", array($baz));

http://www.php.net/manual/en/function.pg-query-params.php

Cheers,
BJ

	pg_query_params is quite slower actually...





Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group