<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.10" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Enterprise Drupal</title>
	<link>http://ken.therickards.com/2007/07/22/enterprise-drupal/</link>
	<description>Ken Rickard's notes about what he's doing</description>
	<pubDate>Mon, 06 Oct 2008 14:19:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.10</generator>

	<item>
		<title>by: Ken Rickard</title>
		<link>http://ken.therickards.com/2007/07/22/enterprise-drupal/#comment-22510</link>
		<pubDate>Tue, 24 Jul 2007 14:37:58 +0000</pubDate>
		<guid>http://ken.therickards.com/2007/07/22/enterprise-drupal/#comment-22510</guid>
					<description>There are generally two paths for wider db support: Write a db abstraction layer (like &lt;a href="http://edin.no-ip.com/html/?q=ready_testing_new_oracle_driver_drupal" rel="nofollow"&gt;Edison Wong&lt;/a&gt; and the Oracle port team), or use Drupal functions to integrate with external data.

See &lt;a href="http://drupal.org/node/131524" rel="nofollow"&gt;this talk I gave&lt;/a&gt; for some ideas.  I should be revising that talk for Barcelona.</description>
		<content:encoded><![CDATA[<p>There are generally two paths for wider db support: Write a db abstraction layer (like <a href="http://edin.no-ip.com/html/?q=ready_testing_new_oracle_driver_drupal" rel="nofollow">Edison Wong</a> and the Oracle port team), or use Drupal functions to integrate with external data.</p>
<p>See <a href="http://drupal.org/node/131524" rel="nofollow">this talk I gave</a> for some ideas.  I should be revising that talk for Barcelona.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Matt</title>
		<link>http://ken.therickards.com/2007/07/22/enterprise-drupal/#comment-22509</link>
		<pubDate>Tue, 24 Jul 2007 14:26:38 +0000</pubDate>
		<guid>http://ken.therickards.com/2007/07/22/enterprise-drupal/#comment-22509</guid>
					<description>This is exactly why it is desirable to have wider db support.  I can't imagine how much I could do w/ an intranet/extranet db that had greater integration with our legacy db (in our case, MSSQL).</description>
		<content:encoded><![CDATA[<p>This is exactly why it is desirable to have wider db support.  I can&#8217;t imagine how much I could do w/ an intranet/extranet db that had greater integration with our legacy db (in our case, MSSQL).
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
