 




<?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: Removing Duplicates</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/removing-duplicates/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/removing-duplicates/</link>
	<description></description>
	<lastBuildDate>Sun, 19 May 2013 03:14:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: carlosdl</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/removing-duplicates/#comment-111274</link>
		<dc:creator>carlosdl</dc:creator>
		<pubDate>Wed, 19 Sep 2012 20:19:34 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/itanswers/removing-duplicates/#comment-111274</guid>
		<description><![CDATA[That might be caused by a bad design.&#160; You should have a main &quot;doctors&quot; table, in which each doctor appears just once, and an additional table were you can store all of the addresses registered for&#160;each doctor.

If the design cannot be changed, you would need something&#160;to differentiate the many records that a doctor can have in the table.&#160; Something like a type of address, or priority, or address&#039; correlative, etc.&#160;]]></description>
		<content:encoded><![CDATA[<p>That might be caused by a bad design.&nbsp; You should have a main &#8220;doctors&#8221; table, in which each doctor appears just once, and an additional table were you can store all of the addresses registered for&nbsp;each doctor.</p>
<p>If the design cannot be changed, you would need something&nbsp;to differentiate the many records that a doctor can have in the table.&nbsp; Something like a type of address, or priority, or address&#8217; correlative, etc.&nbsp;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.012 seconds using memcached
Object Caching 268/271 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-19 23:24:33 -->