<?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: C# How-To: Creating a Driver Foundation</title>
	<atom:link href="http://blog.jstrese.net/article/20/c-how-to-creating-a-driver-foundation/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jstrese.net/article/20/c-how-to-creating-a-driver-foundation/</link>
	<description>A blog about technology and development</description>
	<lastBuildDate>Mon, 08 Jun 2009 20:12:02 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jason</title>
		<link>http://blog.jstrese.net/article/20/c-how-to-creating-a-driver-foundation/comment-page-1/#comment-92</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Wed, 11 Mar 2009 05:09:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jstrese.net/article/20/c-how-to-creating-a-driver-foundation/#comment-92</guid>
		<description>@Michael
You&#039;re correct that I do use the ODBC driver, however there is nothing wrong with using a driver inside another driver. With this example, you could devise an application that works with multiple database types (all using different drivers, connection strings, etc) -- but yes, the end driver is ODBC. There&#039;s nothing wrong with that.

For example, if you wanted to do an application that used PgSQL, MySQL, and SQLite -- you would have to write different application code for all queries (as they don&#039;t all output the same type of objects, nor do they connect the same way). Using my method you could do everything with a simple layer, that would load the correct end-driver.. kind of like a universal driver I guess. You get it, right?</description>
		<content:encoded><![CDATA[<p>@Michael<br />
You&#8217;re correct that I do use the ODBC driver, however there is nothing wrong with using a driver inside another driver. With this example, you could devise an application that works with multiple database types (all using different drivers, connection strings, etc) &#8212; but yes, the end driver is ODBC. There&#8217;s nothing wrong with that.</p>
<p>For example, if you wanted to do an application that used PgSQL, MySQL, and SQLite &#8212; you would have to write different application code for all queries (as they don&#8217;t all output the same type of objects, nor do they connect the same way). Using my method you could do everything with a simple layer, that would load the correct end-driver.. kind of like a universal driver I guess. You get it, right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Sync</title>
		<link>http://blog.jstrese.net/article/20/c-how-to-creating-a-driver-foundation/comment-page-1/#comment-91</link>
		<dc:creator>Michael Sync</dc:creator>
		<pubDate>Mon, 09 Mar 2009 18:26:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jstrese.net/article/20/c-how-to-creating-a-driver-foundation/#comment-91</guid>
		<description>I don&#039;t think this is actual database driver. you are just using Odbc that .Net already provides you.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think this is actual database driver. you are just using Odbc that .Net already provides you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
