get rid of SQL_ASCII?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: get rid of SQL_ASCII?
Date: 2013-09-05 12:47:32
Message-ID: 52287D64.1040800@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Can we consider getting rid of the SQL_ASCII server-side "encoding"? I
don't see any good use for it, and it's often a support annoyance, and
it leaves warts all over the code. This would presumably be a
multi-release effort.

As a first step in accommodating users who have existing SQL_ASCII
databases, we could change SQL_ASCII into a real encoding with
conversion routines to all other encodings that only convert 7-bit ASCII
characters. That way, users who use SQL_ASCII as real ASCII or don't
care could continue to use it. Others would be forced to either set
SQL_ASCII as the client encoding or adjust the encoding on the server.

On the client side, the default libpq client "encoding" SQL_ASCII would
be renamed to something like SAME or whatever, so the behavior would
stay the same.

Other ideas? Are there legitimate uses for SQL_ASCII?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2013-09-05 12:52:02 Re: get rid of SQL_ASCII?
Previous Message Noah Misch 2013-09-05 11:57:39 Re: Is it necessary to rewrite table while increasing the scale of datatype numeric???