<?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 on: MySQL to Oracle Date and Time Helper Functions</title>
	<link>http://www.lamp2lapo.com/2006/11/28/mysql-to-oracle-date-and-time-helper-functions/</link>
	<description>Helping PHP developers migrate from MySQL to Oracle</description>
	<pubDate>Tue, 07 Oct 2008 09:52:11 +0000</pubDate>
	<generator>http://www.orablog.org/?v=0.3+</generator>

	<item>
		<title>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>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>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>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>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>
</channel>
</rss>
