<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: DB: it&#8217;s a matter of balance</title>
	<link>http://www.fissore.org/blog/db-its-a-matter-of-balance/</link>
	<description>When everybody thinks alike, nobody is really thinking</description>
	<pubDate>Tue, 07 Feb 2012 11:46:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: Roberto Franchini</title>
		<link>http://www.fissore.org/blog/db-its-a-matter-of-balance/#comment-10253</link>
		<dc:creator>Roberto Franchini</dc:creator>
		<pubDate>Fri, 05 Oct 2007 07:15:08 +0000</pubDate>
		<guid>http://www.fissore.org/blog/db-its-a-matter-of-balance/#comment-10253</guid>
		<description>Don't steal my business logic! 
I agree with you, and this is a post from a live project (still live after a year, I don't known :) ) :
http://www.request.to.it/frank/index.php?entry=entry061020-102039
Ah, I leaved it!</description>
		<content:encoded><![CDATA[<p>Don&#8217;t steal my business logic!<br />
I agree with you, and this is a post from a live project (still live after a year, I don&#8217;t known :) ) :<br />
<a href="http://www.request.to.it/frank/index.php?entry=entry061020-102039" rel="nofollow">http://www.request.to.it/frank/index.php?entry=entry061020-102039</a><br />
Ah, I leaved it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Federico Fissore</title>
		<link>http://www.fissore.org/blog/db-its-a-matter-of-balance/#comment-10249</link>
		<dc:creator>Federico Fissore</dc:creator>
		<pubDate>Mon, 01 Oct 2007 06:04:24 +0000</pubDate>
		<guid>http://www.fissore.org/blog/db-its-a-matter-of-balance/#comment-10249</guid>
		<description>http://www.agiledata.org/ has some info and a bunch of links about being agile in managing databases

BTW, I would (personally) prefer to have some abstraction layer to take care of it, instead of me. Some ORM lib or ruby's active record with its "migrate" feature</description>
		<content:encoded><![CDATA[<p><a href="http://www.agiledata.org/" rel="nofollow">http://www.agiledata.org/</a> has some info and a bunch of links about being agile in managing databases</p>
<p>BTW, I would (personally) prefer to have some abstraction layer to take care of it, instead of me. Some ORM lib or ruby&#8217;s active record with its &#8220;migrate&#8221; feature</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aladin &#38; the genius</title>
		<link>http://www.fissore.org/blog/db-its-a-matter-of-balance/#comment-10248</link>
		<dc:creator>aladin &#38; the genius</dc:creator>
		<pubDate>Mon, 01 Oct 2007 00:01:15 +0000</pubDate>
		<guid>http://www.fissore.org/blog/db-its-a-matter-of-balance/#comment-10248</guid>
		<description>What about updating db server and to not let dba denormilize well-made databases? I'm a bit scared from using a not reliable database structure. 

Are already present best pratices to build "Agile-DB"?</description>
		<content:encoded><![CDATA[<p>What about updating db server and to not let dba denormilize well-made databases? I&#8217;m a bit scared from using a not reliable database structure. </p>
<p>Are already present best pratices to build &#8220;Agile-DB&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Federico Fissore</title>
		<link>http://www.fissore.org/blog/db-its-a-matter-of-balance/#comment-10247</link>
		<dc:creator>Federico Fissore</dc:creator>
		<pubDate>Sun, 30 Sep 2007 09:50:06 +0000</pubDate>
		<guid>http://www.fissore.org/blog/db-its-a-matter-of-balance/#comment-10247</guid>
		<description>argh, yeah, re-reading it for the Nth time, I too find it a bit hard to get.

The solution is to be pragmatic and to think at the db as a desk drawer. It will happen someday that you'll need it to sync in someway with something else, and so you'll use triggers and stored procedures: just limit the number of them, because your job is to keep the business logic consistent, not to waste time trying to understand why that damn row wasn't inserted into the damn table!

Thank you for the genius ;)</description>
		<content:encoded><![CDATA[<p>argh, yeah, re-reading it for the Nth time, I too find it a bit hard to get.</p>
<p>The solution is to be pragmatic and to think at the db as a desk drawer. It will happen someday that you&#8217;ll need it to sync in someway with something else, and so you&#8217;ll use triggers and stored procedures: just limit the number of them, because your job is to keep the business logic consistent, not to waste time trying to understand why that damn row wasn&#8217;t inserted into the damn table!</p>
<p>Thank you for the genius ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aladin &#38; the genius</title>
		<link>http://www.fissore.org/blog/db-its-a-matter-of-balance/#comment-10246</link>
		<dc:creator>aladin &#38; the genius</dc:creator>
		<pubDate>Sun, 30 Sep 2007 09:25:48 +0000</pubDate>
		<guid>http://www.fissore.org/blog/db-its-a-matter-of-balance/#comment-10246</guid>
		<description>So? Which is the solution? :) Is there a part two for this post?

(pustules! you're a damn genius!)</description>
		<content:encoded><![CDATA[<p>So? Which is the solution? :) Is there a part two for this post?</p>
<p>(pustules! you&#8217;re a damn genius!)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

