Is there any chance of recording the '\' storage behavior as a bug? I
don't
know what kind of bug tracking PostgreSQL has.
I view this as a serious problem. The user of a database should have
complete
confidence that whatever is sent to the back-end actually gets stored,
not altered
because of the existence in the data of one type of character.
In my instance it makes storing windows paths such as
\\Xavier\Manufacturing
impossible. I've got lots of other data that could contain backslashes
that I
couldn't afford to have altered. Sorry to sound alarmist, but this
behavior is a
real show stopper for me.
> -----Original Message-----
> From: James Oden [SMTP:joden@lee.k12.nc.us]
> Sent: Thursday, August 13, 1998 5:47 AM
> To: Bryan Brunton
> Cc: pgsql-interfaces@postgresql.org
> Subject: Re: [INTERFACES] '\' and varchar data type problem w/ MS
> Access and ODBC driver
>
>
>
> >
> >The backslash character '\' seems to cause problems when using the
> >varchar
> >data type. MS Access will refuse to update a varchar field if 3
> >backslashes
> >have been inserted.
> If you want litterally three backslashes you may need to massage the
> data to
> add an extra one before each one, so your three back slashes become
> six back
> slashes. I am just guessing on this, but in postgreSQL's
> implementation of
> SQL (and this may be just a SQL thing) the \ is used as an escape
> sequence,
> much like it is in C. Someone else on the list earlier had a problem
> recreating his databases from a dump because it did have \'s in
> it....james
>
>