<?xml version="1.0" encoding="UTF-8"?><!-- generator="orablog/0.3+" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments for lamp2lapo</title>
	<link>http://www.lamp2lapo.com</link>
	<description>Helping PHP developers migrate from MySQL to Oracle</description>
	<pubDate>Sat, 05 Jul 2008 18:04:38 +0000</pubDate>
	<generator>http://www.orablog.org/?v=0.3+</generator>

	<item>
		<title>Comment on Auto Increment Fields by rebby</title>
		<link>http://www.lamp2lapo.com/2006/11/01/auto-increment-fields/#comment-609</link>
		<pubDate>Tue, 22 Jan 2008 18:54:18 +0000</pubDate>
		<guid>http://www.lamp2lapo.com/2006/11/01/auto-increment-fields/#comment-609</guid>
					<description>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!</description>
		<content:encoded><![CDATA[<p>I took this article one step further to show how this can be done via ADOdb since it&#8217;s not perfectly clear in the ADOdb documentation. See <a href='https://rebby.com/blog.php?detail=31' rel='nofollow'>https://rebby.com/blog.php?detail=31</a> for the details.</p>
<p>Thanks to lamp2lamo for the general framework and bulk of the examples!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on MySQL to Oracle Date and Time Helper Functions by hootbah</title>
		<link>http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-319</link>
		<pubDate>Wed, 04 Apr 2007 13:44:12 +0000</pubDate>
		<guid>http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-319</guid>
					<description>Thanks for the update Herman.</description>
		<content:encoded><![CDATA[<p>Thanks for the update Herman.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on MySQL to Oracle Date and Time Helper Functions by Herman Vierhout</title>
		<link>http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-315</link>
		<pubDate>Wed, 04 Apr 2007 12:30:11 +0000</pubDate>
		<guid>http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-315</guid>
					<description>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 ...</description>
		<content:encoded><![CDATA[<p>Not so smart of me!<br />
Overenthusiastic I proposed something impossible &#8230;:<br />
Package-functions can only have synonyms by their package-name, so the package name still has to be used like Hootbah mentioned.<br />
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&#8217;t be called any news &#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on MySQL to Oracle Date and Time Helper Functions by Herman Vierhout</title>
		<link>http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-22</link>
		<pubDate>Fri, 16 Mar 2007 10:12:46 +0000</pubDate>
		<guid>http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-22</guid>
					<description>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.</description>
		<content:encoded><![CDATA[<p>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.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on MySQL to Oracle Date and Time Helper Functions by hootbah</title>
		<link>http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-9</link>
		<pubDate>Thu, 07 Dec 2006 13:06:25 +0000</pubDate>
		<guid>http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-9</guid>
					<description>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 &lt;em&gt;package_name.function_name&lt;/em&gt;

For example if we wrapped the date functions up into a package called &lt;em&gt;mysql_dates&lt;/em&gt; you would call the now function like:
&lt;pre&gt;SELECT mysql_dates.now FROM dual;&lt;/pre&gt;
As opposed to the method without the package:
&lt;pre&gt;SELECT now FROM dual;&lt;/pre&gt;
To make porting easier its probably better not to wrap these functions in  a package.</description>
		<content:encoded><![CDATA[<p>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.</p>
<p>To call a function in a package you have to call it by <em>package_name.function_name</em></p>
<p>For example if we wrapped the date functions up into a package called <em>mysql_dates</em> you would call the now function like:</p>
<pre>SELECT mysql_dates.now FROM dual;</pre>
<p>As opposed to the method without the package:</p>
<pre>SELECT now FROM dual;</pre>
<p>To make porting easier its probably better not to wrap these functions in  a package.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on MySQL to Oracle Date and Time Helper Functions by RuFuS2</title>
		<link>http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-8</link>
		<pubDate>Wed, 06 Dec 2006 12:00:00 +0000</pubDate>
		<guid>http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/#comment-8</guid>
					<description>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.</description>
		<content:encoded><![CDATA[<p>Wouldn&#8217;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.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on PHP Conference Update: Oracle is free and easy to use! by fifers</title>
		<link>http://www.lamp2lapo.com/2006/11/07/php-conference-update-oracle-is-free-and-easy-to-use/#comment-7</link>
		<pubDate>Mon, 13 Nov 2006 11:59:40 +0000</pubDate>
		<guid>http://www.lamp2lapo.com/2006/11/07/php-conference-update-oracle-is-free-and-easy-to-use/#comment-7</guid>
					<description>Interesting point, Matt. Reviewing the &lt;a href="http://www.mysql.com/company/legal/licensing/commercial-license.html" rel="nofollow"&gt;MySQL Commercial License&lt;/a&gt; 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."</description>
		<content:encoded><![CDATA[<p>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:</p>
<p>&#8220;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.&#8221;</p>
<p>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 &#8220;If you paid for the software then you need to pay for MySQL.&#8221;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on PHP Conference Update: Oracle is free and easy to use! by Matt Vance</title>
		<link>http://www.lamp2lapo.com/2006/11/07/php-conference-update-oracle-is-free-and-easy-to-use/#comment-6</link>
		<pubDate>Sun, 12 Nov 2006 20:33:06 +0000</pubDate>
		<guid>http://www.lamp2lapo.com/2006/11/07/php-conference-update-oracle-is-free-and-easy-to-use/#comment-6</guid>
					<description>I believe your statement that "MySQL is not free to distribute or deploy with non-GPL software" is a bit misleading, if not incorrect. According to the &lt;a href="http://www.mysql.com/company/legal/licensing/opensource-license.html" rel="nofollow"&gt;MySQL Open Source License&lt;/a&gt;, "As long as you never distribute the MySQL Software in any way, you are free to use it for powering your application, irrespective of whether your application is under GPL license or not."</description>
		<content:encoded><![CDATA[<p>I believe your statement that &#8220;MySQL is not free to distribute or deploy with non-GPL software&#8221; is a bit misleading, if not incorrect. According to the <a href="http://www.mysql.com/company/legal/licensing/opensource-license.html" rel="nofollow">MySQL Open Source License</a>, &#8220;As long as you never distribute the MySQL Software in any way, you are free to use it for powering your application, irrespective of whether your application is under GPL license or not.&#8221;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Column Names by TopKat</title>
		<link>http://www.lamp2lapo.com/2006/09/25/column-names/#comment-5</link>
		<pubDate>Fri, 10 Nov 2006 12:21:21 +0000</pubDate>
		<guid>http://www.lamp2lapo.com/2006/09/25/column-names/#comment-5</guid>
					<description>Hi,

Oracle can return case-sensitive column-names:
SQL&#62; create table test (id number, thing varchar2(10));

Table created.

SQL&#62; insert into test(id, thing) values (1, 'One');

1 row created.

SQL&#62; commit;

Commit complete.

SQL&#62; select id as Id, thing as Thing from test;

        ID THING           select id as "Id", thing as "Thing" from test;

        Id Thing          </description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Oracle can return case-sensitive column-names:<br />
SQL&gt; create table test (id number, thing varchar2(10));</p>
<p>Table created.</p>
<p>SQL&gt; insert into test(id, thing) values (1, &#8216;One&#8217;);</p>
<p>1 row created.</p>
<p>SQL&gt; commit;</p>
<p>Commit complete.</p>
<p>SQL&gt; select id as Id, thing as Thing from test;</p>
<p>        ID THING           select id as &#8220;Id&#8221;, thing as &#8220;Thing&#8221; from test;</p>
<p>        Id Thing
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Modifying Oracle XE&#8217;s backup.sh Script to do Incremental Backups by PHP Conference Update: Oracle is free and easy to use! at lamp2lapo</title>
		<link>http://www.lamp2lapo.com/2006/10/04/modifying-oracle-xes-backupsh-script-to-do-incremental-backups/#comment-4</link>
		<pubDate>Tue, 07 Nov 2006 14:29:36 +0000</pubDate>
		<guid>http://www.lamp2lapo.com/2006/10/04/modifying-oracle-xes-backupsh-script-to-do-incremental-backups/#comment-4</guid>
					<description>[...] The second issue is ease of use. It is true that Oracle is quite complex and if you build a serious application using it you will require the services of an Oracle DBA at some point in time. I&#8217;ve seen many MySQL installations in my time and I can confidently say that almost every one should have used the services of a MySQL DBA to tune it correctly. DBA issues aside, Oracle XE provides an easy to use, web-based GUI for performing most tasks. It&#8217;s only when you delve outside of your standard CRUD operations, like modifying the default backup strategy, that Oracle-specific knowledge comes in to play. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The second issue is ease of use. It is true that Oracle is quite complex and if you build a serious application using it you will require the services of an Oracle DBA at some point in time. I&#8217;ve seen many MySQL installations in my time and I can confidently say that almost every one should have used the services of a MySQL DBA to tune it correctly. DBA issues aside, Oracle XE provides an easy to use, web-based GUI for performing most tasks. It&#8217;s only when you delve outside of your standard CRUD operations, like modifying the default backup strategy, that Oracle-specific knowledge comes in to play. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
