Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Bugs > BUG #4098: Enco...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 2 Topic 3689 of 3899
Post > Topic >>

BUG #4098: Encoding problems

by Jan-Peter.Seifert@[EMAIL PROTECTED] ("Jan-Peter Seifert") Apr 7, 2008 at 04:16 PM

The following bug has been logged online:

Bug reference:      4098
Logged by:          Jan-Peter Seifert
Email address:      Jan-Peter.Seifert@[EMAIL PROTECTED]
 version: 8.2
Operating system:   Windows xp
Description:        Encoding problems
Details: 

The encoding of the source db/server is LATIN1. The data type of the field
is text (The storage mode is extended). It's/was possible to add
characters
available in CP1252 but not in LATIN1 like the Euro character (code 80).
When ex****ting to UTF8 via "pg_dump -o -U postgres -E UTF-8 ..." (iconv?)
it
just adds the character with the code "C2" before the Euro character in
the
dump. When im****ting the dump to a server/db with CP1252 it just throws an
error because of the inconvertible character (0xc280) and seems to stop
with
no further error messages (at least the whole table in question is empty
although filled in the source db). It wasn't an issue before the
restrictions were put in place, because the C locale is insufficient.

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
 




 2 Posts in Topic:
BUG #4098: Encoding problems
Jan-Peter.Seifert@[EMAIL   2008-04-07 16:16:12 
Re: BUG #4098: Encoding problems
heikki@[EMAIL PROTECTED]   2008-04-07 18:46:29 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan13V112 Sun Jul 6 1:22:20 CDT 2008.