Received: from rakete.joerdens.de ([62.104.116.221]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f5F8UHa42574 for ; Fri, 15 Jun 2001 04:30:17 -0400 (EDT) (envelope-from frank@rakete.joerdens.de) Received: (from frank@localhost) by rakete.joerdens.de (8.9.3/8.9.3) id KAA25218; Fri, 15 Jun 2001 10:30:11 +0200 Date: Fri, 15 Jun 2001 10:30:11 +0200 From: Frank Joerdens To: Mitch Vincent Cc: pgsql-php@postgresql.org Subject: Re: Re(2): Test (fwd) Message-ID: <20010615103011.A25185@rakete.joerdens.de> References: <009301c0f4da$f9a71b20$330a0a0a@rutgersinsurance.com> <00f301c0f4f7$70ef3c00$330a0a0a@rutgersinsurance.com> <004601c0f525$8b7d3e90$0200000a@Mitch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.2i In-Reply-To: <004601c0f525$8b7d3e90$0200000a@Mitch>; from mvincent@cablespeed.com on Thu, Jun 14, 2001 at 06:57:43PM -0400 X-Subliminal-Message: Use Linux! Use Linux! X-Archive-Number: 200106/34 X-Sequence-Number: 431 On Thu, Jun 14, 2001 at 06:57:43PM -0400, Mitch Vincent wrote: > The apostrophe being a special character in PostgreSQL (and most other > databases), it needs to be escaped if you wish it to go nicely into a > query.. > addslashes() and related functions will help there. > > Another thing to keep in mine is htmlspecialchars() -- it's very useful > when someone might put a double quote in your form field -- which could > seriously mess up when you have something like NAME="Whatever" VALUE="this is what I'm "talking" about"> , sort of thing. Also note that the PHP runtime parameter magic_quotes_gpc is usually on by default which does the escaping by default. - Frank