> Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> >>> This may be the only solution. Converting everything to UTF-8 has
> >>> issues because some encodings are not roundtrip-safe
> >> Is this still true?
> > I beleive so. If use the ICU Converter Explorer  to
> examine some of
> > the encodings we support, they have "Contains ambiguous
> aliases? TRUE".
> Which ones, and are they client-only encodings? If all our
> server-side encodings are round-trip safe then I think
> there's no big issue.
> In any case I don't think there's a huge problem if we say
> that database and user names had better be chosen from the
> round-trip-safe subset.
Doesn't this also affect passwords? If so it might be harder to enforce
as the user is often allowed to pick his own password...
pgsql-hackers by date
|Next:||From: Jim C. Nasby||Date: 2006-02-28 16:22:00|
|Subject: Re: Vacuum dead tuples that are "between" transactions|
|Previous:||From: Tom Lane||Date: 2006-02-28 16:19:02|
|Subject: Re: character encoding in StartupMessage |