| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-advocacy(at)postgresql(dot)org |
| Cc: | Chris Travers <chris(at)travelamericas(dot)com>, "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
| Subject: | Re: [HACKERS] Enticing interns to PostgreSQL |
| Date: | 2005-07-26 21:09:09 |
| Message-ID: | 200507261409.10388.josh@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Chris,
> How hard would it be to automatically create enum_ tables in the back
> ground to emulate MySQL's enum type? Sort of like we do with SERIAL
> datatypes... Part of the problem is that MySQL's enum type is so
> braindead from a database design perspective that most of us would not
> be interested in using it. Emulating an int foreign key for another
> created table might make it ok, though.
The mysql2postgres.pl script actually does this (create enum types). It
would be better to auto-create a table and FK, though.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2005-07-26 21:27:33 | Re: SQL/PSM for 8.2 will offer ANSI/ISO, MySQL, and DB2 Compatibility |
| Previous Message | Jeff Davis | 2005-07-26 21:05:17 | Re: ENUM type |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew - Supernews | 2005-07-26 21:34:33 | Re: More buildfarm stuff |
| Previous Message | Jeff Davis | 2005-07-26 21:05:17 | Re: ENUM type |