| From: | Tommi Maekitalo <t(dot)maekitalo(at)epgmbh(dot)de> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Mysql -> PgSQL |
| Date: | 2002-08-23 05:54:56 |
| Message-ID: | 200208230754.56550.t.maekitalo@epgmbh.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > Thats not so trivial. The type set can have "zero or more values, each of
> > which must be chosen from a list of allowed values" (from Mysql-manual).
> > In PostgreSQL you have to use a details-table for this. This is a
> > nonstandard feature of Mysql (these people concentrate in creating
> > nonstandard extensions before supporting the full standard ;-)
>
> Oh, yes, it is enum that is CHECK. 'set' has multiple values. It is a
> nifty MySQL feature, I must say.
But not so tricky as it looks first. They use just a bitmask for it. The
maximum number of allowed values is limited to 64 so it must be a 8-Byte
bitmask.
What do you think? Wouldn't it be nice to have this feature? It shouldn't be
too hard to implement it.
Tommi
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-08-23 06:24:37 | Excellent DBMS Resource Site |
| Previous Message | Stephan Szabo | 2002-08-23 05:41:41 | Re: Foreign keys: how to turn referential integrity |