Alvaro Herrera <[EMAIL PROTECTED]> writes:
> The problem is that a single application coming from a single
> environment is happy with a 8-bit-unchecked encoding, but as soon as
> they develop a second application using a different environment, which
> uses a different encoding, they start seeing invalid data pop up.
[ shrug... ] The evidence at hand says that many people never get to
that point. For instance, a particular database may never be accessed
through anything except JDBC, and so all the incoming data will be utf8
anyway.
My feeling about it is that we already made significant changes in 8.0
--- it won't default to SQL_ASCII unless your locale is "C", which to me
is a pretty strong indication that you are not very concerned about
encodings. We should wait and see what field experience is like with
that, rather than insisting on anything as anal-retentive as disallowing
8-bit data in SQL_ASCII. Doing that might have technical purity but I
think it will create as many problems as it prevents.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
