<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Beware of this trap when comparing strings in T-SQL with trailing spaces</title>
	<atom:link href="http://improvingsoftware.com/2009/09/09/beware-of-this-trap-when-comparing-strings-in-t-sql-with-trailing-spaces/feed/" rel="self" type="application/rss+xml" />
	<link>http://improvingsoftware.com/2009/09/09/beware-of-this-trap-when-comparing-strings-in-t-sql-with-trailing-spaces/</link>
	<description>Upgrading the software development process one reader at a time.</description>
	<lastBuildDate>Tue, 01 May 2012 06:08:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Equality an trailing spaces in SQL &#171; The Data Specialist</title>
		<link>http://improvingsoftware.com/2009/09/09/beware-of-this-trap-when-comparing-strings-in-t-sql-with-trailing-spaces/#comment-1348</link>
		<dc:creator><![CDATA[Equality an trailing spaces in SQL &#171; The Data Specialist]]></dc:creator>
		<pubDate>Fri, 27 Apr 2012 14:45:57 +0000</pubDate>
		<guid isPermaLink="false">http://improvingsoftware.com/?p=1268#comment-1348</guid>
		<description><![CDATA[[...] A fellow blogger provides more information about this. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] A fellow blogger provides more information about this. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://improvingsoftware.com/2009/09/09/beware-of-this-trap-when-comparing-strings-in-t-sql-with-trailing-spaces/#comment-737</link>
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Wed, 08 Sep 2010 11:57:30 +0000</pubDate>
		<guid isPermaLink="false">http://improvingsoftware.com/?p=1268#comment-737</guid>
		<description><![CDATA[I&#039;ve run into this before, but have forgotten about it.  Thanks for the reminder.

In situations that might present padded spaces, I tend to use RTRIM(), as they are typically of no use.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve run into this before, but have forgotten about it.  Thanks for the reminder.</p>
<p>In situations that might present padded spaces, I tend to use RTRIM(), as they are typically of no use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken</title>
		<link>http://improvingsoftware.com/2009/09/09/beware-of-this-trap-when-comparing-strings-in-t-sql-with-trailing-spaces/#comment-352</link>
		<dc:creator><![CDATA[Ken]]></dc:creator>
		<pubDate>Wed, 09 Sep 2009 18:09:31 +0000</pubDate>
		<guid isPermaLink="false">http://improvingsoftware.com/?p=1268#comment-352</guid>
		<description><![CDATA[I&#039;m intimately familiar with this scenario.  I&#039;ve been building a .NET front end for older FoxPro tables, and FoxPro always pads any varchar with spaces until it fills all available space of the field.  I prefer to pad each value to the max length when doing comparison, as stated in the KB article.  I think it&#039;s more readable and intuitive.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m intimately familiar with this scenario.  I&#8217;ve been building a .NET front end for older FoxPro tables, and FoxPro always pads any varchar with spaces until it fills all available space of the field.  I prefer to pad each value to the max length when doing comparison, as stated in the KB article.  I think it&#8217;s more readable and intuitive.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

