<?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: Should ODBC Classes have a Syntax Layer?</title>
	<atom:link href="http://trentrichardson.com/2009/12/28/should-odbc-classes-have-a-syntax-layer/feed/" rel="self" type="application/rss+xml" />
	<link>http://trentrichardson.com/2009/12/28/should-odbc-classes-have-a-syntax-layer/</link>
	<description>practical web design &#38; development</description>
	<lastBuildDate>Tue, 07 Sep 2010 11:25:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: trent</title>
		<link>http://trentrichardson.com/2009/12/28/should-odbc-classes-have-a-syntax-layer/comment-page-1/#comment-14196</link>
		<dc:creator>trent</dc:creator>
		<pubDate>Mon, 28 Dec 2009 21:14:50 +0000</pubDate>
		<guid isPermaLink="false">http://trentrichardson.com/?p=438#comment-14196</guid>
		<description>Thats a good point, it could also be useful for version specific differences even for regular mysql or mssql connections, even when not using odbc</description>
		<content:encoded><![CDATA[<p>Thats a good point, it could also be useful for version specific differences even for regular mysql or mssql connections, even when not using odbc</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jay</title>
		<link>http://trentrichardson.com/2009/12/28/should-odbc-classes-have-a-syntax-layer/comment-page-1/#comment-14191</link>
		<dc:creator>jay</dc:creator>
		<pubDate>Mon, 28 Dec 2009 13:04:14 +0000</pubDate>
		<guid isPermaLink="false">http://trentrichardson.com/?p=438#comment-14191</guid>
		<description>this approach might also be useful for different version db, sql server 2008 may have some features not available for sql server 2000, and those workarounds could be available through the syntax layer.</description>
		<content:encoded><![CDATA[<p>this approach might also be useful for different version db, sql server 2008 may have some features not available for sql server 2000, and those workarounds could be available through the syntax layer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.379 seconds -->
