| From: | Joe <svn(at)freedomcircle(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dawid Kuroczko <qnex42(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Converting MySQL tinyint to PostgreSQL |
| Date: | 2005-07-12 22:27:47 |
| Message-ID: | 42D443E3.60606@freedomcircle.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera wrote:
> On Tue, Jul 12, 2005 at 05:37:32PM -0400, Joe wrote:
>
>>If it stored character data in Unicode (UCS-16) it would always take
>>up two-bytes per character.
>
> Really? We don't support UCS-16, for good reasons (we'd have to rewrite
> several parts of the code in order to support '0' bytes embedded in
> strings ... we use regular C strings extensively).
I'm sorry. I meant to say UCS-2, which by definition uses 16 bits = 2 octets =
2 bytes. To support an even larger code space, you could use UCS-4 which always
uses 4 bytes.
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-07-12 22:31:20 | Re: Converting MySQL tinyint to PostgreSQL |
| Previous Message | Alvaro Herrera | 2005-07-12 22:10:48 | Re: Converting MySQL tinyint to PostgreSQL |