<?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: Query on the Long Column or Field</title>
	<atom:link href="http://geeksbloggingat.com/2009/10/07/query-on-the-long-column-or-field/feed/" rel="self" type="application/rss+xml" />
	<link>http://geeksbloggingat.com/2009/10/07/query-on-the-long-column-or-field/</link>
	<description>Let&#039;s share...</description>
	<lastBuildDate>Fri, 05 Aug 2011 10:11:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Nitin Jain</title>
		<link>http://geeksbloggingat.com/2009/10/07/query-on-the-long-column-or-field/comment-page-1/#comment-1618</link>
		<dc:creator>Nitin Jain</dc:creator>
		<pubDate>Sat, 10 Oct 2009 06:47:56 +0000</pubDate>
		<guid isPermaLink="false">http://geeksbloggingat.com/?p=829#comment-1618</guid>
		<description>Hi Ashruf,

I agree with you! I have already discussed the same in the post above too :-)

Yet, there are times when you need to find all XMLs with a particular entity, say, all outbound XMLs for Confirming the order. Or in the cases where the ID based search is not working for you in the Interface Logs, the search on the Long column and parse through the entire XML becomes important.

You can employ the tip above in such scenarios!

Cheers..</description>
		<content:encoded><![CDATA[<p>Hi Ashruf,</p>
<p>I agree with you! I have already discussed the same in the post above too <img src='http://geeksbloggingat.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Yet, there are times when you need to find all XMLs with a particular entity, say, all outbound XMLs for Confirming the order. Or in the cases where the ID based search is not working for you in the Interface Logs, the search on the Long column and parse through the entire XML becomes important.</p>
<p>You can employ the tip above in such scenarios!</p>
<p>Cheers..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashrufunnisa</title>
		<link>http://geeksbloggingat.com/2009/10/07/query-on-the-long-column-or-field/comment-page-1/#comment-1607</link>
		<dc:creator>Ashrufunnisa</dc:creator>
		<pubDate>Fri, 09 Oct 2009 07:01:34 +0000</pubDate>
		<guid isPermaLink="false">http://geeksbloggingat.com/?p=829#comment-1607</guid>
		<description>You can always store the xml and an identifier for the record like interface name which will help you to find the exact record of failure.
As such you can also store any unique ID which can help in finding the record, like activity Id, order Id, account Id and all..Thi sreally helps..In our project we do the same and finding a record which has failed and working on it is very easy.....</description>
		<content:encoded><![CDATA[<p>You can always store the xml and an identifier for the record like interface name which will help you to find the exact record of failure.<br />
As such you can also store any unique ID which can help in finding the record, like activity Id, order Id, account Id and all..Thi sreally helps..In our project we do the same and finding a record which has failed and working on it is very easy&#8230;..</p>
]]></content:encoded>
	</item>
</channel>
</rss>

