http://www.lamp2lapo.com/2007/04/01/emulating-mysql-enum-columns/ Helping PHP developers migrate from MySQL to Oracle Tue, 07 Oct 2008 10:05:46 +0000 http://www.orablog.org/?v=0.3+ http://www.lamp2lapo.com/2007/04/01/emulating-mysql-enum-columns/#comment-636 Thu, 25 Sep 2008 10:33:15 +0000 http://www.lamp2lapo.com/2007/04/01/emulating-mysql-enum-columns/#comment-636 Agreed. In an implementation with millions of rows it would make a big savings. You would probably use a cross-reference table in Oracle if space was a concern in your application. Another advantage of using a cross-reference table is that you can modify the parameters at run-time. Enum and the Oracle-equivalent does lock you in to that set of choices until you alter the table structure. When creating schemas from scratch we generally avoid enums in MySQL for this very reason. This trick is most useful for adding Oracle support to an application designed for MySQL. Agreed. In an implementation with millions of rows it would make a big savings. You would probably use a cross-reference table in Oracle if space was a concern in your application. Another advantage of using a cross-reference table is that you can modify the parameters at run-time. Enum and the Oracle-equivalent does lock you in to that set of choices until you alter the table structure. When creating schemas from scratch we generally avoid enums in MySQL for this very reason. This trick is most useful for adding Oracle support to an application designed for MySQL.

]]> http://www.lamp2lapo.com/2007/04/01/emulating-mysql-enum-columns/#comment-635 Thu, 25 Sep 2008 05:51:53 +0000 http://www.lamp2lapo.com/2007/04/01/emulating-mysql-enum-columns/#comment-635 I hope Oracle implements some kind of enum type like mysql. The problem with the Oracle version is that the table will be larger as compared to the mysql version since it stores the entire text entry while in the mysql enum, it only stores the index number since the representation is stored in the table definition. I hope Oracle implements some kind of enum type like mysql. The problem with the Oracle version is that the table will be larger as compared to the mysql version since it stores the entire text entry while in the mysql enum, it only stores the index number since the representation is stored in the table definition.

]]>