| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Gregory Youngblood <pgcluster(at)netio(dot)org> |
| Cc: | 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 03:24:25 |
| Message-ID: | 42E84FE9.9020705@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-general |
> I think one of the more difficult areas will be to convert unsigned
> fields from mysql into postgres. For smaller sizes it is possible to
> convert to postgres by moving one size up and using constraints to
> restrict numbers to be positive, and possibly within the mysql range
> too. But, 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 just issue a warning...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2005-07-28 03:34:56 | Re: MySQL to PostgreSQL, was ENUM type |
| Previous Message | Gregory Youngblood | 2005-07-28 02:58:05 | Re: [pgsql-advocacy] MySQL to PostgreSQL, was ENUM type |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tony Caduto | 2005-07-28 03:31:30 | Re: GUID for postgreSQL |
| Previous Message | Gregory Youngblood | 2005-07-28 02:58:05 | Re: [pgsql-advocacy] MySQL to PostgreSQL, was ENUM type |