Skip site navigation (1) Skip section navigation (2)

Re: bytea char escaping

From: "Ivar" <ivar(at)lumisoft(dot)ee>
To: pgsql-general(at)postgresql(dot)org
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: bytea char escaping
Date: 2003-06-25 07:39:07
Message-ID: bdbjia$5tf$1@main.gmane.org (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-patches
If I encode bytes as utf8 I get right result.

I guess that uncicode odbc driver returns bytes as utf8, is it so ?

"Ivar" <ivar(at)lumisoft(dot)ee> wrote in message
news:bdbhf9$v6n$1(at)main(dot)gmane(dot)org(dot)(dot)(dot)
>
> Yes this is much clearer.
>
> I got this part working, but some some chars is handled wrong.
> I'm using 7.3.1 in windows.
>
> eg. alt 152 is handeld wrong.
>
> there is some encoding problems, any ideas ?
> "Joe Conway" <mail(at)joeconway(dot)com> wrote in message
> news:3EF93DF4(dot)3030507(at)joeconway(dot)com(dot)(dot)(dot)
> Stephen Robert Norris wrote:
> > Well, no. What it says is that certain values must be escaped (but
> > doesn't say which ones). Then it says there are alternate escape
> > sequences for some values, which it lists.
> >
> > It doesn't say "The following table contains the characters which must
> > be escaped:", which would be much clearer (and actually useful).
>
> Attached documentation patch updates the wording for bytea input
> escaping, per complaint by Stephen Norris above.
>
> Please apply.
>
> Joe
>
>
>
> --------------------------------------------------------------------------
--
> ----
>
>
> Index: doc/src/sgml/datatype.sgml
> =================================================================== RCS
> file: /opt/src/cvs/pgsql-server/doc/src/sgml/datatype.sgml,v retrieving
> revision 1.119 diff -c -r1.119 datatype.sgml ***
doc/src/sgml/datatype.sgml
> 25 Jun 2003 03:50:52 -0000 1.119 --- doc/src/sgml/datatype.sgml 25 Jun
2003
> 06:19:28 -0000 *************** *** 1062,1069 **** literal in an SQL
> statement. In general, to escape an octet, it is converted into the
> three-digit octal number equivalent of its decimal octet value, and
preceded
> by two ! backslashes. Some octet values have alternate escape sequences,
as
> ! shown in . --- 1062,1070 ---- literal in an SQL statement. In general,
to
> escape an octet, it is converted into the three-digit octal number
> equivalent of its decimal octet value, and preceded by two ! backslashes.
> contains the ! characters which must be escaped, and gives the alternate
> escape ! sequences where applicable.
>
> --------------------------------------------------------------------------
--
> ----
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
>                http://www.postgresql.org/docs/faqs/FAQ.html
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>




In response to

pgsql-patches by date

Next:From: Michael MeskesDate: 2003-06-25 10:50:09
Subject: Re: %x, %g warnings
Previous:From: IvarDate: 2003-06-25 07:03:23
Subject: Re: bytea char escaping

pgsql-general by date

Next:From: Bjorn T JohansenDate: 2003-06-25 08:40:16
Subject: Updating an emty table?
Previous:From: Christopher Kings-LynneDate: 2003-06-25 07:11:00
Subject: Re: [GENERAL] Physical Database Configuration

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group