Thread: Re: [GENERAL] bytea char escaping
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
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@joeconway.com> wrote in message
news:3EF93DF4.3030507@joeconway.com...
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
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@lumisoft.ee> wrote in message news:bdbhf9$v6n$1@main.gmane.org... > > 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@joeconway.com> wrote in message > news:3EF93DF4.3030507@joeconway.com... > 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 >
Patch applied. Thanks. --------------------------------------------------------------------------- Joe Conway wrote: > 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 [ text/html is unsupported, treating like TEXT/PLAIN ] > 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 <acronym>SQL</acronym> 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 <xref linkend="datatype-binary-sqlesc">. > </para> > > <table id="datatype-binary-sqlesc"> > --- 1062,1070 ---- > literal in an <acronym>SQL</acronym> 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. <xref linkend="datatype-binary-sqlesc"> contains the > ! characters which must be escaped, and gives the alternate escape > ! sequences where applicable. > </para> > > <table id="datatype-binary-sqlesc"> > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073