Search Postgresql Archives

Re: Convert string to UNICODE & migration FROM 7.4 to 9.1

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

 



Philippe Lang <philippe.lang@xxxxxxxxxxxxxx> writes:
> I have a function under PG 7.4 that returns an xml structure, with the content encoded in UNICODE.

Basically, the only reason you got away with that in 7.4 is that 7.4 is
so lax about encodings.  In general, in modern releases, all text
strings inside the backend are in the database's specified encoding.
Full stop, no exceptions.  If you think you need something different,
you need to rethink your assumptions.

I'd try just dropping the convert() step and see what happens.

			regards, tom lane

-- 
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