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

Re: UTF8 encoding and non-text data types

From: Joe <dev(at)freedomcircle(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Medi Montaseri <montaseri(at)gmail(dot)com>, Steve Midgley <public(at)misuse(dot)org>, pgsql-sql(at)postgresql(dot)org
Subject: Re: UTF8 encoding and non-text data types
Date: 2008-01-14 23:03:17
Message-ID: 478BEA35.1010405@freedomcircle.net (view raw or flat)
Thread:
Lists: pgsql-sql
Tom Lane wrote:
> "Medi Montaseri" <montaseri(at)gmail(dot)com> writes:
>   
>> insert into t1 (c1, cost) values ('tewt', 1234)
>> this works find....
>> insert into t1 (c1, cost) values ('&#1588;&#1583;',
>> &#1777;&#1778;&#1779;&#1780;)
>>  DBD::Pg::db do failed: ERROR:  syntax error at or near ";" at character 59,
>>     
>
> Well, you've got two problems there.  The first and biggest is that
> &#NNN; is an HTML notation, not a SQL notation; no SQL database is going
> to think that that string in its input is a representation of a single
> Unicode character.  The other problem is that even if this did happen,
> code points 1777 and nearby are not digits; they're something or other
> in Arabic, apparently.
>   
Precisely. 1777 through 1780 decimal equate to code points U+06F1 
through U+06F4, which correspond to the Arabic numerals 1 through 4.

Joe

In response to

Responses

pgsql-sql by date

Next:From: Tom LaneDate: 2008-01-14 23:24:33
Subject: Re: UTF8 encoding and non-text data types
Previous:From: Tom LaneDate: 2008-01-14 22:41:23
Subject: Re: UTF8 encoding and non-text data types

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