pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedPostgreSQL Handling of Special Characters
6+ messages / 5 participants
[nested] [flat]
* PostgreSQL Handling of Special Characters
@ 2006-03-20 03:30 Christian Paul B. Cosinas <cpc@cybees.com>
0 siblings, 2 replies; 6+ messages in thread
From: Christian Paul B. Cosinas @ 2006-03-20 03:30 UTC (permalink / raw)
To: pgsql-sql; +Cc: 'Christian Paul B. Cosinas' <cpc@cybees.com>
Hi to all,
I am currently using PostgreSQL 8.0.3
My Database uses SQL_ASCII encoding.
I have a program in Visual Basic that connects to PostgreSQL using ODBC
Connection through File DSN.
I insert a text in one fields of my table.
For example, I insert a special character to that field.
Let's say a character of 150 ASCII code. Which looks like a hypen.
When I retrieve the value of that field it gives me a question mark
character instead of that 150 ASCII code character.
What could be the possible reason of this?
Is there a setting in the database configuration to understand that such
special characters?
Please..I really need an answer to this..
Thanks You.
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PostgreSQL Handling of Special Characters
@ 2006-03-20 04:09 Markus Bertheau <mbertheau.pg@googlemail.com>
parent: Christian Paul B. Cosinas <cpc@cybees.com>
1 sibling, 1 reply; 6+ messages in thread
From: Markus Bertheau @ 2006-03-20 04:09 UTC (permalink / raw)
To: Christian Paul B. Cosinas <cpc@cybees.com>; +Cc: pgsql-sql
2006/3/20, Christian Paul B. Cosinas <cpc@cybees.com>:
> Let's say a character of 150 ASCII code. Which looks like a hypen.
>
> When I retrieve the value of that field it gives me a question mark
> character instead of that 150 ASCII code character.
>
> What could be the possible reason of this?
Perhaps the ODBC driver thinks SQL_ASCII means ASCII and therefore
discards all bytes > 127. On PostgreSQL SQL_ASCII really means
SQL_ANYTHING, so to speak. Try to use for the database the encoding
you really use.
Markus Bertheau
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PostgreSQL Handling of Special Characters
@ 2006-03-20 05:48 Christian Paul B. Cosinas <cpc@cybees.com>
parent: Markus Bertheau <mbertheau.pg@googlemail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Christian Paul B. Cosinas @ 2006-03-20 05:48 UTC (permalink / raw)
To: 'Markus Bertheau' <mbertheau.pg@googlemail.com>; +Cc: pgsql-sql
Hi Markus,
Can you please elaborate more on this.
I'm really lost.
Thank You So Much.
-----Original Message-----
From: Markus Bertheau [mailto:mbertheau.pg@googlemail.com]
Sent: Sunday, March 19, 2006 8:09 PM
To: Christian Paul B. Cosinas
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] PostgreSQL Handling of Special Characters
2006/3/20, Christian Paul B. Cosinas <cpc@cybees.com>:
> Let's say a character of 150 ASCII code. Which looks like a hypen.
>
> When I retrieve the value of that field it gives me a question mark
> character instead of that 150 ASCII code character.
>
> What could be the possible reason of this?
Perhaps the ODBC driver thinks SQL_ASCII means ASCII and therefore discards
all bytes > 127. On PostgreSQL SQL_ASCII really means SQL_ANYTHING, so to
speak. Try to use for the database the encoding you really use.
Markus Bertheau
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PostgreSQL Handling of Special Characters
@ 2006-03-20 06:19 Eugene E. <sad@bankir.ru>
parent: Christian Paul B. Cosinas <cpc@cybees.com>
0 siblings, 0 replies; 6+ messages in thread
From: Eugene E. @ 2006-03-20 06:19 UTC (permalink / raw)
To: pgsql-sql
Christian Paul B. Cosinas wrote:
> Hi Markus,
>
> Can you please elaborate more on this.
> I'm really lost.
Be sure that postgresql ITSELF is handling all chars transparently
except ZEROES.
Look for the error in the media layer
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PostgreSQL Handling of Special Characters
@ 2006-03-20 07:34 Peter Eisentraut <peter_e@gmx.net>
parent: Christian Paul B. Cosinas <cpc@cybees.com>
1 sibling, 1 reply; 6+ messages in thread
From: Peter Eisentraut @ 2006-03-20 07:34 UTC (permalink / raw)
To: pgsql-sql; +Cc: Christian Paul B. Cosinas <cpc@cybees.com>
Christian Paul B. Cosinas wrote:
> My Database uses SQL_ASCII encoding.
Do yourself a favor and use something else.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PostgreSQL Handling of Special Characters
@ 2006-03-20 07:49 PFC <lists@peufeu.com>
parent: Peter Eisentraut <peter_e@gmx.net>
0 siblings, 0 replies; 6+ messages in thread
From: PFC @ 2006-03-20 07:49 UTC (permalink / raw)
To: pgsql-sql
>> My Database uses SQL_ASCII encoding.
I just received an email with all accented characters destroyed. UNICODE
should be the default for anything in 2006.
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2006-03-20 07:49 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-03-20 03:30 PostgreSQL Handling of Special Characters Christian Paul B. Cosinas <cpc@cybees.com>
2006-03-20 04:09 ` Markus Bertheau <mbertheau.pg@googlemail.com>
2006-03-20 05:48 ` Christian Paul B. Cosinas <cpc@cybees.com>
2006-03-20 06:19 ` Eugene E. <sad@bankir.ru>
2006-03-20 07:34 ` Peter Eisentraut <peter_e@gmx.net>
2006-03-20 07:49 ` PFC <lists@peufeu.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox