| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Joe <svn(at)freedomcircle(dot)net>, 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-13 04:15:03 |
| Message-ID: | 13061.1121228103@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> Personally I would settle for a fuller set of small fixed size datatypes. The
> "char" datatype is pretty much exactly what's needed except that it provides
> such a quirky interface.
I'm not actually against inventing an int1/tinyint type. I used to be
worried that it would screw up the numeric datatype promotion hierarchy
even more than it already was screwed up :-( ... but I think we have
dealt with most of those issues now. It'd be worth trying anyway ---
much more so than trying to optimize char(1), IMHO.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nee.mem (倪明) | 2005-07-13 04:42:31 | How to use rollback in function with 'pgsql'? |
| Previous Message | Greg Stark | 2005-07-13 03:50:52 | Re: Converting MySQL tinyint to PostgreSQL |