Received: from gw.heart.com.au (mail.hcs.com.au [203.12.235.237]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4B18XA42021 for ; Thu, 10 May 2001 21:08:35 -0400 (EDT) (envelope-from keith@heart.com.au) Received: from tardis.heart.com.au (IDENT:root@tardis.heart.com.au [192.168.0.42]) by gw.heart.com.au (8.9.3/8.9.3) with ESMTP id LAA17313 for ; Fri, 11 May 2001 11:33:29 +1000 Received: from heart.com.au ([192.168.0.65]) by tardis.heart.com.au (8.9.3/8.8.7) with ESMTP id LAA06670 for ; Fri, 11 May 2001 11:08:16 +1000 Message-ID: <3AFB3C52.315C48F0@heart.com.au> Date: Fri, 11 May 2001 11:11:46 +1000 From: Keith Gray X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: PostgreSQL Subject: Escape Quotes Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200105/81 X-Sequence-Number: 2882 When using apostrophies the PostgreSQL string seems to like an escape character as follows: update client set code = 'O\'SHEA' where clientid = 2; The ANSI-92 standard seems to suggest that this could/should be handled by ::= ' ::= update client set code = 'O''SHEA' where clientid = 2; Is it possible to get/configure PostgreSQL to handle as within a dleimited string? Keith Gray