<?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"
	>
<channel>
	<title>Comments on: Keeping track of user-made changes</title>
	<atom:link href="http://www.shanesherman.com/2006/03/28/keeping-track-of-user-made-changes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.shanesherman.com/2006/03/28/keeping-track-of-user-made-changes/</link>
	<description>Random stuff from some dude in Austin Texas</description>
	<pubDate>Sun, 05 Jul 2009 20:30:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Turn of the Crank &#187; Keeping track of user-made changes - Part 2</title>
		<link>http://www.shanesherman.com/2006/03/28/keeping-track-of-user-made-changes/#comment-3</link>
		<dc:creator>Turn of the Crank &#187; Keeping track of user-made changes - Part 2</dc:creator>
		<pubDate>Wed, 10 May 2006 17:40:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.turnofthecrank.com/2006/03/28/keeping-track-of-user-made-changes/#comment-3</guid>
		<description>[...] In my Keeping track of user-made changes post I descriped the various options for implementing change-tracking in my application. I ended up doing something completely different. Ruby on Rails has a cool feature called Observers which basically act like database triggers. After certain events(save, update, create, etc) happen your observer code will automatically get executed. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] In my Keeping track of user-made changes post I descriped the various options for implementing change-tracking in my application. I ended up doing something completely different. Ruby on Rails has a cool feature called Observers which basically act like database triggers. After certain events(save, update, create, etc) happen your observer code will automatically get executed. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: a-train</title>
		<link>http://www.shanesherman.com/2006/03/28/keeping-track-of-user-made-changes/#comment-2</link>
		<dc:creator>a-train</dc:creator>
		<pubDate>Sat, 29 Apr 2006 15:42:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.turnofthecrank.com/2006/03/28/keeping-track-of-user-made-changes/#comment-2</guid>
		<description>I would serialize the diff.  I would imagine if the app gets big and entries grow, the most scalabe option would be to serialize diff.  Once implemented it would serve small and large communities equally with the added benefits of data stores low.  i wouldnt worry so much for the table definition... just roll with the punches if a change is necessary.  i wouldn't let that hold u up.</description>
		<content:encoded><![CDATA[<p>I would serialize the diff.  I would imagine if the app gets big and entries grow, the most scalabe option would be to serialize diff.  Once implemented it would serve small and large communities equally with the added benefits of data stores low.  i wouldnt worry so much for the table definition&#8230; just roll with the punches if a change is necessary.  i wouldn&#8217;t let that hold u up.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
