<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: ⇥ Some thoughts on the MySQL/Oracle merger</title>
	<atom:link href="http://blog.tabini.ca/2009/10/some-thoughts-on-the-mysqloracle-merger/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tabini.ca/2009/10/some-thoughts-on-the-mysqloracle-merger/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=some-thoughts-on-the-mysqloracle-merger</link>
	<description>Stumbling on since 1997</description>
	<lastBuildDate>Fri, 07 Oct 2011 08:06:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Marco Tabini</title>
		<link>http://blog.tabini.ca/2009/10/some-thoughts-on-the-mysqloracle-merger/comment-page-1/#comment-482</link>
		<dc:creator>Marco Tabini</dc:creator>
		<pubDate>Mon, 19 Oct 2009 14:38:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tabini.ca/?p=173#comment-482</guid>
		<description>Jim/Kevin: good points on both counts. My rationale for excluding Postgres is that I feel its community/support ecosystem is not as well developed as that of MySQL. However, I should have mentioned that in the post :-)

Stuart: I was trying to look at the problem from a business perspective—and Drizzle or MariaDB are not viable options there, at least at the moment. As far as MSSQL goes, as I said, there needs to be a realignment; obviously, as you point out, it needs to go beyond the licensing.</description>
		<content:encoded><![CDATA[<p>Jim/Kevin: good points on both counts. My rationale for excluding Postgres is that I feel its community/support ecosystem is not as well developed as that of MySQL. However, I should have mentioned that in the post <img src='http://blog.tabini.ca/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Stuart: I was trying to look at the problem from a business perspective—and Drizzle or MariaDB are not viable options there, at least at the moment. As far as MSSQL goes, as I said, there needs to be a realignment; obviously, as you point out, it needs to go beyond the licensing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://blog.tabini.ca/2009/10/some-thoughts-on-the-mysqloracle-merger/comment-page-1/#comment-481</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Mon, 19 Oct 2009 14:29:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tabini.ca/?p=173#comment-481</guid>
		<description>How does a post of this nature stay free of any talk of PostgreSQL until KevinBruce brought it up in the comments?  Shameful.  Well done KevinBruce--PostgreSQL FTW!</description>
		<content:encoded><![CDATA[<p>How does a post of this nature stay free of any talk of PostgreSQL until KevinBruce brought it up in the comments?  Shameful.  Well done KevinBruce&#8211;PostgreSQL FTW!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Herbert</title>
		<link>http://blog.tabini.ca/2009/10/some-thoughts-on-the-mysqloracle-merger/comment-page-1/#comment-480</link>
		<dc:creator>Stuart Herbert</dc:creator>
		<pubDate>Mon, 19 Oct 2009 14:20:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tabini.ca/?p=173#comment-480</guid>
		<description>Hey Marco,

Interesting thoughts.  Couple of things perhaps to add?

MSSQL isn&#039;t an option for folks who deploy their PHP code on Linux.  All the excellent work MSFT has been putting into the MSSQL drivers for PHP only works in PHP for Windows.  If you&#039;re on Linux, and you want to talk to MSSQL, you&#039;re stuck with the (now ancient) FreeTDS support (which doesn&#039;t support MSSQL 2000 or later fully) or fighting with the major pain that is ODBC.

And that&#039;s ignoring the fact that the new MSSQL drivers aren&#039;t even bundled with PHP 5.3 at this time ...

You didn&#039;t mention Drizzle or MariaDB or the fact that more and more folks are starting to rely on releases from folks like Percona.  Even if Oracle do turn out to be bad custodians of MySQL, there are others willing to step up and ensure a fork has a long and healthy life.  Given the absolute mess Sun have made of MySQL since they acquired it, that might be for the best.

Best regards,
Stu</description>
		<content:encoded><![CDATA[<p>Hey Marco,</p>
<p>Interesting thoughts.  Couple of things perhaps to add?</p>
<p>MSSQL isn&#8217;t an option for folks who deploy their PHP code on Linux.  All the excellent work MSFT has been putting into the MSSQL drivers for PHP only works in PHP for Windows.  If you&#8217;re on Linux, and you want to talk to MSSQL, you&#8217;re stuck with the (now ancient) FreeTDS support (which doesn&#8217;t support MSSQL 2000 or later fully) or fighting with the major pain that is ODBC.</p>
<p>And that&#8217;s ignoring the fact that the new MSSQL drivers aren&#8217;t even bundled with PHP 5.3 at this time &#8230;</p>
<p>You didn&#8217;t mention Drizzle or MariaDB or the fact that more and more folks are starting to rely on releases from folks like Percona.  Even if Oracle do turn out to be bad custodians of MySQL, there are others willing to step up and ensure a fork has a long and healthy life.  Given the absolute mess Sun have made of MySQL since they acquired it, that might be for the best.</p>
<p>Best regards,<br />
Stu</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KevinBruce</title>
		<link>http://blog.tabini.ca/2009/10/some-thoughts-on-the-mysqloracle-merger/comment-page-1/#comment-479</link>
		<dc:creator>KevinBruce</dc:creator>
		<pubDate>Mon, 19 Oct 2009 14:18:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tabini.ca/?p=173#comment-479</guid>
		<description>Don&#039;t forget the PostGresSQL option. That is still a viable and robust alternative which works wonderfully in the LAMP (LAPP?) stack.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t forget the PostGresSQL option. That is still a viable and robust alternative which works wonderfully in the LAMP (LAPP?) stack.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

