From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Volkan YAZICI <volkan.yazici@gmail.com>
Cc: Adam Witney <awitney@sgul.ac.uk>
Cc: pgsql-php <pgsql-php@postgresql.org>
Subject: Re: Automatically opening pdf files stored in a bytea field
Date: Thu, 13 Oct 2005 10:13:29 +0800
Message-ID: <434DC2C9.9020304@familyhealth.com.au> (raw)
In-Reply-To: <7104a7370510121008h198d5013vdd29c30394984855@mail.gmail.com>
References: <BF715966.4EE66%awitney@sgul.ac.uk>
<434C66E0.8060801@familyhealth.com.au>
<7104a7370510121008h198d5013vdd29c30394984855@mail.gmail.com>
> Yep, I agree. Furthermore, (un)escape routines will consume so much
> system CPU. If you can, try to use parameters (pg_query_params() and
> pg_send_params()) in any bytea/lo storage. This makes you free from
> escaping without any potential SQL Injection threats.
PostgreSQL prepared statements don't escape bytea afaik
Chris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-php@postgresql.org
Cc: chriskl@familyhealth.com.au, volkan.yazici@gmail.com, awitney@sgul.ac.uk
Subject: Re: Automatically opening pdf files stored in a bytea field
In-Reply-To: <434DC2C9.9020304@familyhealth.com.au>
References: <BF715966.4EE66%awitney@sgul.ac.uk> <434C66E0.8060801@familyhealth.com.au> <7104a7370510121008h198d5013vdd29c30394984855@mail.gmail.com> <434DC2C9.9020304@familyhealth.com.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox