| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: UTF8 with BOM support in psql |
| Date: | 2009-11-17 14:08:12 |
| Message-ID: | 4B02AE4C.5060904@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Itagaki Takahiro wrote:
> Multi-byte scripts
> without encoding are always dangerous whether BOM is present or not.
> I'd say we can always throw an error when we find queries that contain
> multi-byte characters if no prior encoding declaration.
>
>
>
You will break a gazillion scripts that today work quite happily if you do.
I think you have really not thought out these proposals well.
Maybe there is a case for a extra command line switch to set the initial
client encoding for psql, which would make that a little easier and less
obscure to do. Would that make things simpler for you?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-11-17 14:16:10 | Re: patch - Report the schema along table name in a referential failure error message |
| Previous Message | Greg Sabino Mullane | 2009-11-17 14:01:26 | Re: Raising the geqo_threshold default |