Re: [SQL] UTF8 encoding and non-text data types

At 02:22 PM 1/13/2008, [EMAIL PROTECTED] wrote: Date: Sat, 12 Jan 2008 14:21:00 -0800 From: "Medi Montaseri" <[EMAIL PROTECTED]> To: pgsql-sql@postgresql.org Subject: UTF8 encoding and non-text data types Message-ID: <[EMAIL PROTECTED]> I understand PG supports UTF-8 encoding and I have sucess

Re: [SQL] UTF8 encoding and non-text data types

Thanks Steve, Actually I do not insert text data into my numeric field. As I mentioned given create table t1 { name text, cost decimal } then I would like to insert numeric data into column "cost" because then I can later benefit from numerical operators like SUM, AVG, etc More specifically, I am

Re: [SQL] UTF8 encoding and non-text data types

"Medi Montaseri" <[EMAIL PROTECTED]> writes: > More specifically, I am using HTML, Perl and PG. So from the HTML point of > view a textfield is just some strings. So my user would enter 12345 but > expressed in UTF8. Perl would get this and use DBI to insert it into PG > What I am experiencing now

Re: [SQL] UTF8 encoding and non-text data types

Hi Steve, Have you tried converting to a decimal type or cast for the cost field? If you are gathering this data from a text field and placing in a variable of type string then using that variable in the insert statement it may be rejected because it is not type decimal. This has been my expe

Re: [SQL] UTF8 encoding and non-text data types

Sorry this should have been addressed to Medi dana. Hi Steve, Have you tried converting to a decimal type or cast for the cost field? If you are gathering this data from a text field and placing in a variable of type string then using that variable in the insert statement it may be rejected

Re: [SQL] UTF8 encoding and non-text data types

On Jan 13, 2008 8:51 PM, Steve Midgley <[EMAIL PROTECTED]> wrote: At 02:22 PM 1/13/2008, [EMAIL PROTECTED] wrote: >Date: Sat, 12 Jan 2008 14:21:00 -0800 >From: "Medi Montaseri" < [EMAIL PROTECTED]> >To:

Re: [SQL] UTF8 encoding and non-text data types

Here is my traces from perl CGI code, I'll include two samples one in ASCII and one UTF so we know what to expect Here is actual SQL statement being executed in Perl and DBI. I do not quote the numerical value, just provided to DBI raw. insert into t1 (c1, cost) values ('tewt', 1234) this works f

Re: [SQL] UTF8 encoding and non-text data types

At 12:43 PM 1/14/2008, Medi Montaseri wrote: Here is my traces from perl CGI code, I'll include two samples one in ASCII and one UTF so we know what to expect Here is actual SQL statement being executed in Perl and DBI. I do not quote the numerical value, just provided to DBI raw. insert int

Re: [SQL] UTF8 encoding and non-text data types

"Medi Montaseri" <[EMAIL PROTECTED]> writes: > insert into t1 (c1, cost) values ('tewt', 1234) > this works find > insert into t1 (c1, cost) values ('شد', > ۱۲۳۴) > DBD::Pg::db do failed: ERROR: syntax error at or near ";" at character 59, Well, you've got two problems there. The first and

Re: [SQL] UTF8 encoding and non-text data types

Joe <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> 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 o

Re: [SQL] UTF8 encoding and non-text data types

Tom Lane wrote: "Medi Montaseri" <[EMAIL PROTECTED]> writes: insert into t1 (c1, cost) values ('tewt', 1234) this works find insert into t1 (c1, cost) values ('شد', ۱۲۳۴) DBD::Pg::db do failed: ERROR: syntax error at or near ";" at character 59, Well, you've got two problems ther

Re: [SQL] UTF8 encoding and non-text data types

Tom Lane wrote: Oh? Interesting. But even if we wanted to teach Postgres about that, wouldn't there be a pretty strong risk of getting confused by Arabic's right-to-left writing direction? Wouldn't be real helpful if the entry came out as 4321 when the user wanted 1234. Definitely seems like

Re: [SQL] UTF8 encoding and non-text data types

"Joe" <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> Oh? Interesting. But even if we wanted to teach Postgres about that, >> wouldn't there be a pretty strong risk of getting confused by Arabic's >> right-to-left writing direction? Wouldn't be real helpful if the entry >> came out as 4321 whe

Re: [SQL] UTF8 encoding and non-text data types

Joe writes: > The Arabic language is written right-to-left, except ... when it comes to > numbers. Perhaps they read their numbers right to left but use a little-endian notation. -- John Hasler [EMAIL PROTECTED] Elmwood, WI USA ---(end of broadcast)--