<?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: QlikView 9: Export Document Layout to XML</title>
	<atom:link href="http://andpointsbeyond.com/2009/04/29/qlikview-9-export-layout-to-xml/feed/" rel="self" type="application/rss+xml" />
	<link>http://andpointsbeyond.com/2009/04/29/qlikview-9-export-layout-to-xml/</link>
	<description>mostly about data</description>
	<lastBuildDate>Wed, 01 Feb 2012 00:58:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: QlikCommunity &#124; A Brief Look at QlikView Storage - The QlikView Blogroll</title>
		<link>http://andpointsbeyond.com/2009/04/29/qlikview-9-export-layout-to-xml/comment-page-1/#comment-11370</link>
		<dc:creator>QlikCommunity &#124; A Brief Look at QlikView Storage - The QlikView Blogroll</dc:creator>
		<pubDate>Tue, 05 Oct 2010 03:49:09 +0000</pubDate>
		<guid isPermaLink="false">http://andpointsbeyond.com/?p=317#comment-11370</guid>
		<description>[...] October 2010 (3)September 2010 (15)August 2010 (3)July 2010 (9)June 2010 (15)May 2010 (9)April 2010 (18)March 2010 (13)February 2010 (14)January 2010 (16)December 2009 (9)November 2009 (23)October 2009 (42)September 2009 (27)August 2009 (22)July 2009 (18)June 2009 (19)May 2009 (13)April 2009 (21)March 2009 (12)February 2009 (9)January 2009 (8)December 2008 (10)November 2008 (5)October 2008 (3)September 2008 (6)August 2008 (1)May 2008 (3)              You can learn a lot about how QlikView stores data in memory by looking at how it stores data on disk in QVDs. QVDs are QlikView&#8217;s proprietary data storage format. QVDs are in a format optimized for reading into memory. A QVD stores one QlikView table. Each column is stored separately. Only the unique values [...] Related posts:QlikView 9: Export Document Layout to XML [...]</description>
		<content:encoded><![CDATA[<p>[...] October 2010 (3)September 2010 (15)August 2010 (3)July 2010 (9)June 2010 (15)May 2010 (9)April 2010 (18)March 2010 (13)February 2010 (14)January 2010 (16)December 2009 (9)November 2009 (23)October 2009 (42)September 2009 (27)August 2009 (22)July 2009 (18)June 2009 (19)May 2009 (13)April 2009 (21)March 2009 (12)February 2009 (9)January 2009 (8)December 2008 (10)November 2008 (5)October 2008 (3)September 2008 (6)August 2008 (1)May 2008 (3)              You can learn a lot about how QlikView stores data in memory by looking at how it stores data on disk in QVDs. QVDs are QlikView&#8217;s proprietary data storage format. QVDs are in a format optimized for reading into memory. A QVD stores one QlikView table. Each column is stored separately. Only the unique values [...] Related posts:QlikView 9: Export Document Layout to XML [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: QlikCommunity &#124; The Year in QlikView - The QlikView Blogroll</title>
		<link>http://andpointsbeyond.com/2009/04/29/qlikview-9-export-layout-to-xml/comment-page-1/#comment-8319</link>
		<dc:creator>QlikCommunity &#124; The Year in QlikView - The QlikView Blogroll</dc:creator>
		<pubDate>Sat, 17 Apr 2010 13:33:18 +0000</pubDate>
		<guid isPermaLink="false">http://andpointsbeyond.com/?p=317#comment-8319</guid>
		<description>[...] in QlikView 9&#8230; QlikView 9 adds a powerful new feature to Set Analysis....QlikView 9: Export Document Layout to XML One of the new features in QlikView 9 is &#8220;Export... Related posts brought to you by Yet [...]</description>
		<content:encoded><![CDATA[<p>[...] in QlikView 9&#8230; QlikView 9 adds a powerful new feature to Set Analysis&#8230;.QlikView 9: Export Document Layout to XML One of the new features in QlikView 9 is &#8220;Export&#8230; Related posts brought to you by Yet [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Posts about xml as of April 29, 2009 &#124; Shirasmane</title>
		<link>http://andpointsbeyond.com/2009/04/29/qlikview-9-export-layout-to-xml/comment-page-1/#comment-2442</link>
		<dc:creator>Posts about xml as of April 29, 2009 &#124; Shirasmane</dc:creator>
		<pubDate>Thu, 07 May 2009 08:12:22 +0000</pubDate>
		<guid isPermaLink="false">http://andpointsbeyond.com/?p=317#comment-2442</guid>
		<description>[...]  [...]</description>
		<content:encoded><![CDATA[<p>[...]  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Jakosky</title>
		<link>http://andpointsbeyond.com/2009/04/29/qlikview-9-export-layout-to-xml/comment-page-1/#comment-2367</link>
		<dc:creator>Jay Jakosky</dc:creator>
		<pubDate>Mon, 04 May 2009 19:18:17 +0000</pubDate>
		<guid isPermaLink="false">http://andpointsbeyond.com/?p=317#comment-2367</guid>
		<description>I agree, Ralf. I combined two thoughts into one idea that isn&#039;t clear. There are tools and scripts available to create differentials of XML. And it&#039;s easy to push the XML into a standard version control system.</description>
		<content:encoded><![CDATA[<p>I agree, Ralf. I combined two thoughts into one idea that isn&#8217;t clear. There are tools and scripts available to create differentials of XML. And it&#8217;s easy to push the XML into a standard version control system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ralf Becher</title>
		<link>http://andpointsbeyond.com/2009/04/29/qlikview-9-export-layout-to-xml/comment-page-1/#comment-2361</link>
		<dc:creator>Ralf Becher</dc:creator>
		<pubDate>Mon, 04 May 2009 15:38:42 +0000</pubDate>
		<guid isPermaLink="false">http://andpointsbeyond.com/?p=317#comment-2361</guid>
		<description>Hi Jay,
we definitely will use this for versioning and metadata tracking. But a diff of two of these XML files will be very difficult. Could it be a good idea to use a XML database instead of versionig tool (or additional)?
Ralf</description>
		<content:encoded><![CDATA[<p>Hi Jay,<br />
we definitely will use this for versioning and metadata tracking. But a diff of two of these XML files will be very difficult. Could it be a good idea to use a XML database instead of versionig tool (or additional)?<br />
Ralf</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Qlikview - Nice Reads (Analyse field usage; applymap instead of join; XML export; Wolters Kluwers health) &#124; Quick - Qlear - Qool</title>
		<link>http://andpointsbeyond.com/2009/04/29/qlikview-9-export-layout-to-xml/comment-page-1/#comment-2213</link>
		<dc:creator>Qlikview - Nice Reads (Analyse field usage; applymap instead of join; XML export; Wolters Kluwers health) &#124; Quick - Qlear - Qool</dc:creator>
		<pubDate>Wed, 29 Apr 2009 14:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://andpointsbeyond.com/?p=317#comment-2213</guid>
		<description>[...] Fourth: a great post from Jay Jakosky about version 9 XML export: QlikView 9: Export Document Layout to XML [...]</description>
		<content:encoded><![CDATA[<p>[...] Fourth: a great post from Jay Jakosky about version 9 XML export: QlikView 9: Export Document Layout to XML [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

