<?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: Separation of Data and View</title>
	<atom:link href="http://moverve.com/blog/2007/03/separation-of-data-and-view/feed/" rel="self" type="application/rss+xml" />
	<link>http://moverve.com/blog/2007/03/separation-of-data-and-view/</link>
	<description>... tools and techniques of the management accountant</description>
	<pubDate>Thu, 11 Mar 2010 14:09:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris</title>
		<link>http://moverve.com/blog/2007/03/separation-of-data-and-view/comment-page-1/#comment-131</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 20 Mar 2007 01:35:42 +0000</pubDate>
		<guid isPermaLink="false">http://moverve.com/blog/2007/03/separation-of-data-and-view/#comment-131</guid>
		<description>Agreed.  The MVC model is a generally good idea.  Even when it is often implemented in ways that could leave something to be desired.

If you want to take a look at some really un-MVC code, look into that in SQL-Ledger ;-)

I am actually a fan of the idea that, when doing relational database management-based apps, as much of the model should be in the database as possible.  We can then define a model such that it requires minimal code to wrap it, and thus allow for better business tools to be added on.</description>
		<content:encoded><![CDATA[<p>Agreed.  The MVC model is a generally good idea.  Even when it is often implemented in ways that could leave something to be desired.</p>
<p>If you want to take a look at some really un-MVC code, look into that in SQL-Ledger ;-)</p>
<p>I am actually a fan of the idea that, when doing relational database management-based apps, as much of the model should be in the database as possible.  We can then define a model such that it requires minimal code to wrap it, and thus allow for better business tools to be added on.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
