| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gregory Youngblood <pgcluster(at)netio(dot)org> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Chris Travers <chris(at)travelamericas(dot)com>, Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>, "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>, PostgreSQL advocacy <pgsql-advocacy(at)postgresql(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] MySQL to PostgreSQL, was ENUM type |
| Date: | 2005-07-28 04:53:07 |
| Message-ID: | 20242.1122526387@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-general |
Gregory Youngblood <pgcluster(at)netio(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Youngblood | 2005-07-28 04:57:57 | Re: [pgsql-advocacy] MySQL to PostgreSQL, was ENUM type |
| Previous Message | Chris Travers | 2005-07-28 04:16:04 | Re: [GENERAL] MySQL to PostgreSQL, was ENUM type |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Youngblood | 2005-07-28 04:57:57 | Re: [pgsql-advocacy] MySQL to PostgreSQL, was ENUM type |
| Previous Message | Chris Travers | 2005-07-28 04:16:04 | Re: [GENERAL] MySQL to PostgreSQL, was ENUM type |