Received: from w-ux2.os-net.de (root@w-ux2.os-net.de [195.248.130.2]) by
	hub.org (8.8.8/8.7.5) with ESMTP id KAA06195 for
	<pgsql-interfaces@postgresql.org>;
	Sun, 23 Aug 1998 10:36:34 -0400 (EDT)
Received: from os-net.de (root@di7.wertron.de [195.248.128.71]) by
	w-ux2.os-net.de (8.7.5/8.7.3) with ESMTP id PAA11199 for
	<pgsql-interfaces@postgresql.org>; Sun, 23 Aug 1998 15:31:04 +0200
X-Ncc-Regid: de.wertron
Sender: root@w-ux2.os-net.de
Message-ID: <35E029E7.2637E001@os-net.de>
Date: Sun, 23 Aug 1998 16:40:39 +0200
From: Rolf Luettecke <rl@os-net.de>
X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.35 i586)
MIME-Version: 1.0
To: pgsql-interfaces@postgresql.org
Subject: Backslash-problem
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Bruce,

I had difficulties to insert varchar/text data into a table,
because the data contains "Backslashes". The problem occured
during access from the "webside" (apache/perl/DBD) and by
accessing the table from M$-Access/ODBC (Vers. ...249) too.
To work around the problem, I deleted a lot of stuff in
the sourcefile: .../src/backend/parser/scansup.c:

...
        for (i = 0, j = 0; i < len; i++)
        {
                newStr[j] = s[i];
                j++;
        }
        newStr[j] = '\0';
        return newStr;
...

Now it seems to work ok, inserts from both frontends are
stored correctly - but what is the dark-side of this hack ???

Regards
Rolf Luettecke