Comments for lamp2lapo http://www.lamp2lapo.com Helping PHP developers migrate from MySQL to Oracle Sat, 04 Jul 2009 05:24:34 +0000 http://www.orablog.org/?v=0.3+ Comment on Emulating MySQL ENUM Columns by fifers 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.

]]> Comment on Emulating MySQL ENUM Columns by baroto 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.

]]> Comment on Moving to Oracle by leandro http://www.lamp2lapo.com/2006/09/20/moving-to-oracle/#comment-634 Fri, 19 Sep 2008 16:11:13 +0000 http://www.lamp2lapo.com/2006/09/20/moving-to-oracle/#comment-634 Wrong choice. Go for PostgreSQL: it is already as fast as Oracle, no arbitrary limits, it is soon to be even faster, no need to pay for lots of options, much more standards-compliant, and it is much more featured about programming — think PL/PSM, boolean data types, PL/Scheme, PL/Java, PL/Ruby, PL/bash, PL/Python — and have I mentioned it is fast, it is free software, and enables great programming? Wrong choice. Go for PostgreSQL: it is already as fast as Oracle, no arbitrary limits, it is soon to be even faster, no need to pay for lots of options, much more standards-compliant, and it is much more featured about programming — think PL/PSM, boolean data types, PL/Scheme, PL/Java, PL/Ruby, PL/bash, PL/Python — and have I mentioned it is fast, it is free software, and enables great programming?

]]> Comment on Auto Increment Fields by rebby http://www.lamp2lapo.com/2006/11/01/auto-increment-fields/#comment-609 Tue, 22 Jan 2008 18:54:18 +0000 http://www.lamp2lapo.com/2006/11/01/auto-increment-fields/#comment-609 I took this article one step further to show how this can be done via ADOdb since it's not perfectly clear in the ADOdb documentation. See https://rebby.com/blog.php?detail=31 for the details. Thanks to lamp2lamo for the general framework and bulk of the examples! I took this article one step further to show how this can be done via ADOdb since it’s not perfectly clear in the ADOdb documentation. See https://rebby.com/blog.php?detail=31 for the details.

Thanks to lamp2lamo for the general framework and bulk of the examples!

]]> Comment on MySQL to Oracle Date and Time Helper Functions by hootbah http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-319 Wed, 04 Apr 2007 13:44:12 +0000 http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-319 Thanks for the update Herman. Thanks for the update Herman.

]]> Comment on MySQL to Oracle Date and Time Helper Functions by Herman Vierhout http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-315 Wed, 04 Apr 2007 12:30:11 +0000 http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-315 Not so smart of me! Overenthusiastic I proposed something impossible ...: Package-functions can only have synonyms by their package-name, so the package name still has to be used like Hootbah mentioned. What can be done is use one schema to place all conversion functions in so you can use the synonyms proposed (to avoid using the schema-name) and can easily maintain them. But that can't be called any news ... Not so smart of me!
Overenthusiastic I proposed something impossible …:
Package-functions can only have synonyms by their package-name, so the package name still has to be used like Hootbah mentioned.
What can be done is use one schema to place all conversion functions in so you can use the synonyms proposed (to avoid using the schema-name) and can easily maintain them. But that can’t be called any news …

]]> Comment on MySQL to Oracle Date and Time Helper Functions by Herman Vierhout http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-22 Fri, 16 Mar 2007 10:12:46 +0000 http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-22 Using a package is a good idea (maintainability) and in combination with synonyms exactly like the MySql function names (without the package prefix) makes it easy to use as well. Using a package is a good idea (maintainability) and in combination with synonyms exactly like the MySql function names (without the package prefix) makes it easy to use as well.

]]> Comment on MySQL to Oracle Date and Time Helper Functions by hootbah http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-9 Thu, 07 Dec 2006 13:06:25 +0000 http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-9 It would be a good idea to wrap the functions in a package. However in doing this you would have to change all the sql queries where one of these function is being used. To call a function in a package you have to call it by <em>package_name.function_name</em> For example if we wrapped the date functions up into a package called <em>mysql_dates</em> you would call the now function like: <pre>SELECT mysql_dates.now FROM dual;</pre> As opposed to the method without the package: <pre>SELECT now FROM dual;</pre> To make porting easier its probably better not to wrap these functions in a package. It would be a good idea to wrap the functions in a package. However in doing this you would have to change all the sql queries where one of these function is being used.

To call a function in a package you have to call it by package_name.function_name

For example if we wrapped the date functions up into a package called mysql_dates you would call the now function like:

SELECT mysql_dates.now FROM dual;

As opposed to the method without the package:

SELECT now FROM dual;

To make porting easier its probably better not to wrap these functions in a package.

]]> Comment on MySQL to Oracle Date and Time Helper Functions by RuFuS2 http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-8 Wed, 06 Dec 2006 12:00:00 +0000 http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-8 Wouldn't it be better to create an Oracle Package to contain the Functions? That way it can be extended to include any other functionality required. Wouldn’t it be better to create an Oracle Package to contain the Functions? That way it can be extended to include any other functionality required.

]]> Comment on PHP Conference Update: Oracle is free and easy to use! by fifers http://www.lamp2lapo.com/2006/11/07/php-conference-update-oracle-is-free-and-easy-to-use/#comment-7 Mon, 13 Nov 2006 11:59:40 +0000 http://www.lamp2lapo.com/2006/11/07/php-conference-update-oracle-is-free-and-easy-to-use/#comment-7 Interesting point, Matt. Reviewing the <a href="http://www.mysql.com/company/legal/licensing/commercial-license.html" rel="nofollow">MySQL Commercial License</a> gives you a slightly different spin on that statement: "If you develop and distribute a commercial application and as part of utilizing your application, the end-user must download a copy of MySQL; for each derivative work, you (or, in some cases, your end-user) need a commercial license for the MySQL server and/or MySQL client libraries." It would appear that for developing an Intranet application you would be fine but if you purchase software such as vBulletin and run it on your server then you require a MySQL license. My interpretation of the spirit of the license can be summarised by "If you paid for the software then you need to pay for MySQL." Interesting point, Matt. Reviewing the MySQL Commercial License gives you a slightly different spin on that statement:

“If you develop and distribute a commercial application and as part of utilizing your application, the end-user must download a copy of MySQL; for each derivative work, you (or, in some cases, your end-user) need a commercial license for the MySQL server and/or MySQL client libraries.”

It would appear that for developing an Intranet application you would be fine but if you purchase software such as vBulletin and run it on your server then you require a MySQL license. My interpretation of the spirit of the license can be summarised by “If you paid for the software then you need to pay for MySQL.”

]]>