On Fri, Jul 29, 2005 at 02:49:54PM -0500, Jim C. Nasby wrote:
> On Thu, Jul 28, 2005 at 12:53:07AM -0400, Tom Lane wrote:
> > Gregory Youngblood <pgcluster@netio.org> writes:
> > > ... the problem is unsigned bigint in mysql to postgresql.
> > > There's not another larger integer size that can be used that would
> > > allow the 18446744073709551615 (is that the max value?) max value
> > > available in mysql. Or am I missing something?
> >
> > You'd have to translate that to NUMERIC, which would work but would
> > take a bit of a performance hit ...
>
> Is there any serious impediment to adding unsigned types to PostgreSQL?
> They should be as readily supported as signed, right? I don't think
> these would even have to be in core, if that's a concern.
Tom mentioned a couple of days ago that the worst problems that would be
created by adding more numeric types are solved as of 8.1.
--
Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
"Before you were born your parents weren't as boring as they are now. They
got that way paying your bills, cleaning up your room and listening to you
tell them how idealistic you are." -- Charles J. Sykes' advice to teenagers
