| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>, Bill Moran <wmoran(at)potentialtech(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Why do we let CREATE DATABASE reassign encoding? |
| Date: | 2009-04-23 19:27:05 |
| Message-ID: | 49F0C109.8010109@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> If we wanted to be entirely anal about this, we could allow SQL_ASCII
> destination with a different source encoding, but not the reverse.
> However, we currently consider that you're on your own to ensure sanity
> when using SQL_ASCII as far as locale goes, so I'm not sure why the
> policy would be different for encoding.
>
>
>
The trouble is that people won't know the provenance of their database.
I think we should try to guarantee as far as possible that if a database
has encoding X then all the data in it is valid in that encoding.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2009-04-23 19:32:16 | Re: Why do we let CREATE DATABASE reassign encoding? |
| Previous Message | Tom Lane | 2009-04-23 19:10:17 | Re: Why do we let CREATE DATABASE reassign encoding? |