From: | nholtz(at)docuweb(dot)ca (Neal Holtz) |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: EVAL and SET equivalents in PostgreSQL |
Date: | 2002-07-05 10:30:52 |
Message-ID: | 639f17f8.0207050230.7af0edcc@posting.google.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I just noticed this in Freshmeat - it may be helpful.
"Perl utility to convert MySQL dumps into Postgres dump.
(MySQL and Postgres are the most popular and advanced
open-source database engines.) Emulates ENUMs and
SETs via user types and operators."
"Since version 7.1beta5, my2pg is a part of Postgres
distribution and can be found in the collection of
contributed code under contrib/mysql directory."
http://ziet.zhitomir.ua./~fonin/code/
cjs(at)cynic(dot)net (Curt Sampson) wrote in message news:<Pine(dot)NEB(dot)4(dot)44(dot)0207050915111(dot)22637-100000(at)angelic(dot)cynic(dot)net>...
> On Wed, 3 Jul 2002, Lynn David Newton wrote:
>
> > No one who has responded (four people so far) has yet
> > quite hit the nail on the head regarding a substitute
> > for MySQL's SET data type.
>
> Well, as someone else pointed out, there's always the option of
> doing it the relational way, and just creating a separate table
> for this.
>
> However, if you want to do what MySQL does internally, and do it
> in a more portable way, you can just use bitfields in an int or
...
From | Date | Subject | |
---|---|---|---|
Next Message | caroline kenny | 2002-07-05 10:51:42 | Re: Carraige Return issues |
Previous Message | Oliver Elphick | 2002-07-05 09:48:15 | Re: Carraige Return issues |