Re: [pgsql-advocacy] MySQL to PostgreSQL, was ENUM type - Mailing list pgsql-general

From Tom Lane
Subject Re: [pgsql-advocacy] MySQL to PostgreSQL, was ENUM type
Date
Msg-id 20242.1122526387@sss.pgh.pa.us
Whole thread Raw
In response to Re: [pgsql-advocacy] MySQL to PostgreSQL, was ENUM type  (Gregory Youngblood <pgcluster@netio.org>)
Responses Re: [pgsql-advocacy] MySQL to PostgreSQL, was ENUM type  (Gregory Youngblood <pgcluster@netio.org>)
Re: [pgsql-advocacy] MySQL to PostgreSQL, was ENUM type  (Kenneth Marshall <ktm@it.is.rice.edu>)
Re: [pgsql-advocacy] MySQL to PostgreSQL, was ENUM type  ("Jim C. Nasby" <decibel@decibel.org>)
List pgsql-general
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 ...

            regards, tom lane

pgsql-general by date:

Previous
From: Chris Travers
Date:
Subject: Re: [pgsql-advocacy] MySQL to PostgreSQL, was ENUM type
Next
From: Gregory Youngblood
Date:
Subject: Re: [pgsql-advocacy] MySQL to PostgreSQL, was ENUM type