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.
--
Jim C. Nasby, Database Consultant decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
