X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 7E63AD8267 for ; Wed, 12 Oct 2005 23:09:33 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 79770-09 for ; Thu, 13 Oct 2005 02:09:29 +0000 (GMT) Received: from houston.familyhealth.com.au (houston.au.fhnetwork.com [203.22.197.21]) by svr1.postgresql.org (Postfix) with ESMTP id 6055BD825E for ; Wed, 12 Oct 2005 23:09:30 -0300 (ADT) Received: from houston.familyhealth.com.au (localhost [127.0.0.1]) by houston.familyhealth.com.au (Postfix) with ESMTP id C930C2505B; Thu, 13 Oct 2005 10:09:26 +0800 (WST) Received: from [127.0.0.1] (work-40.internal [192.168.0.40]) by houston.familyhealth.com.au (Postfix) with ESMTP id 3AE7E24FF7; Thu, 13 Oct 2005 10:09:25 +0800 (WST) Message-ID: <434DC2C9.9020304@familyhealth.com.au> Date: Thu, 13 Oct 2005 10:13:29 +0800 From: Christopher Kings-Lynne User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Volkan YAZICI Cc: Adam Witney , pgsql-php Subject: Re: Automatically opening pdf files stored in a bytea field References: <434C66E0.8060801@familyhealth.com.au> <7104a7370510121008h198d5013vdd29c30394984855@mail.gmail.com> In-Reply-To: <7104a7370510121008h198d5013vdd29c30394984855@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-familyhealth-MailScanner-Information: Please contact the ISP for more information X-familyhealth-MailScanner: Found to be clean X-familyhealth-MailScanner-From: chriskl@familyhealth.com.au X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.061 required=5 tests=[AWL=0.011, FORGED_RCVD_HELO=0.05] X-Spam-Level: X-Archive-Number: 200510/28 X-Sequence-Number: 3296 > 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