<?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: Hybrid Static/Dynamic content with SQLite</title>
	<atom:link href="http://www.stephenbeattie.com/2008/05/12/hybrid-staticdynamic-content-with-sqlite/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stephenbeattie.com/2008/05/12/hybrid-staticdynamic-content-with-sqlite/</link>
	<description>Flash, PHP, Flex and other RIA technologies.</description>
	<lastBuildDate>Mon, 29 Jun 2009 13:08:33 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Content Modeling with XML</title>
		<link>http://www.stephenbeattie.com/2008/05/12/hybrid-staticdynamic-content-with-sqlite/comment-page-1/#comment-52</link>
		<dc:creator>Content Modeling with XML</dc:creator>
		<pubDate>Tue, 20 May 2008 08:35:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.stephenbeattie.com/2008/05/12/hybrid-staticdynamic-content-with-sqlite/#comment-52</guid>
		<description>[...] And so, the XML simply defines a form to be rendered but also, the fact that we have a record of the structure of the stored content means that we can use this to publish content from the database into HTML (by means of templating), XML (by using the &#8216;id&#8217; attribute of each property node as the tag names) and even to an SQLite database. Since SQLite supports only a few simple data types I was able to simply map the property types (taking into account their validation rules) and create an SQLite database for each Collection on the fly. This proved to be an ideal solution for reasons I&#8217;ve mentioned before. [...]</description>
		<content:encoded><![CDATA[<p>[...] And so, the XML simply defines a form to be rendered but also, the fact that we have a record of the structure of the stored content means that we can use this to publish content from the database into HTML (by means of templating), XML (by using the &#8216;id&#8217; attribute of each property node as the tag names) and even to an SQLite database. Since SQLite supports only a few simple data types I was able to simply map the property types (taking into account their validation rules) and create an SQLite database for each Collection on the fly. This proved to be an ideal solution for reasons I&#8217;ve mentioned before. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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