Search Postgresql Archives

Re: Problem with encoding

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/25/11 11:14 AM, SUBHAM ROY wrote:
While loading data from shape files, the default encoding type is UTF8. It reports an error "couldn't convert to UTF8 ... change the encoding to latin1 ... etc."


what reported this?

So my question is, if one table say T1 is loaded using UTF8 and the other say T2 is loaded using say LATIN1, then does it impose any problem while querying, i.e. while running queries.

different client_encoding, or server encoding? you can't mix server encodings, but the client could in theory switch client_encoding back and forth as it executes various queries, that would be a pain in the butt.



--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux