Philippe Lang 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
Hi,
I'm migrating a PG 7.4 database (encoded in LATIN1) to PG 9.1. The upgrade is
just fine, except a problem with a conversion to UNICODE for which I was not
able to find a solution yet:
I have a function under PG 7.4 that returns an xml structure, with the content
encoded in UNICODE.
The fu
