| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Salem Berhanu" <salemb4(at)hotmail(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] postgres & server encodings |
| Date: | 2005-08-09 15:59:27 |
| Message-ID: | 16705.1123603167@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
"Salem Berhanu" <salemb4(at)hotmail(dot)com> writes:
> What exactly is the SQL_ASCII encoding in postgres?
SQL_ASCII isn't so much an encoding as the declaration that you don't
care about encodings. That setting simply disables encoding validity
checks and encoding conversions. The server will take any byte string
clients send it (barring only embedded zero bytes), and store and return
it unchanged.
Since it disables conversions, the notion of converting to another
encoding is pretty much meaningless :-(.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2005-08-09 15:59:46 | Re: postgres & server encodings |
| Previous Message | John DeSoi | 2005-08-09 14:55:52 | Re: REVOKE from all tables ... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2005-08-09 15:59:46 | Re: postgres & server encodings |
| Previous Message | Tom Lane | 2005-08-09 15:54:33 | Re: Reference new.* or old.* in dynamic statement? |