<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: The Ruby on Rails way for Model naming</title>
	<atom:link href="http://mr-purpleduck.me.uk/2007/08/30/the-ruby-on-rails-way-for-model-naming/feed/" rel="self" type="application/rss+xml" />
	<link>http://mr-purpleduck.me.uk/2007/08/30/the-ruby-on-rails-way-for-model-naming/</link>
	<description>Photography, Security and a little bit of every day life</description>
	<lastBuildDate>Wed, 16 Mar 2011 20:35:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: mrpurpleduck</title>
		<link>http://mr-purpleduck.me.uk/2007/08/30/the-ruby-on-rails-way-for-model-naming/#comment-114</link>
		<dc:creator><![CDATA[mrpurpleduck]]></dc:creator>
		<pubDate>Fri, 31 Aug 2007 18:38:36 +0000</pubDate>
		<guid isPermaLink="false">http://mrpurpleduck.wordpress.com/2007/08/30/the-ruby-on-rails-way-for-model-naming/#comment-114</guid>
		<description><![CDATA[Craig:

Yes, they are just date fields.

I did not mean the &lt;i&gt;primary key&lt;/i&gt;, I was meaning the main context for the data in a table row. In other tables (e.g. purchase_orders, the PO number is stored in the name column). I was thinking that in the hardware table, the field serial_number should be name instead.

As for test, yes I have learned my lesson. Needing to add 90 unit tests, before moving onto functional tests was a mistake. This refactoring will be painful to complete.

I&#039;ll also need to add functional tests for all of the controllers as well. But I&#039;ll fall in that pit when I come to it (i.e. after the unit tests).]]></description>
		<content:encoded><![CDATA[<p>Craig:</p>
<p>Yes, they are just date fields.</p>
<p>I did not mean the <i>primary key</i>, I was meaning the main context for the data in a table row. In other tables (e.g. purchase_orders, the PO number is stored in the name column). I was thinking that in the hardware table, the field serial_number should be name instead.</p>
<p>As for test, yes I have learned my lesson. Needing to add 90 unit tests, before moving onto functional tests was a mistake. This refactoring will be painful to complete.</p>
<p>I&#8217;ll also need to add functional tests for all of the controllers as well. But I&#8217;ll fall in that pit when I come to it (i.e. after the unit tests).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Webster</title>
		<link>http://mr-purpleduck.me.uk/2007/08/30/the-ruby-on-rails-way-for-model-naming/#comment-112</link>
		<dc:creator><![CDATA[Craig Webster]]></dc:creator>
		<pubDate>Fri, 31 Aug 2007 10:08:59 +0000</pubDate>
		<guid isPermaLink="false">http://mrpurpleduck.wordpress.com/2007/08/30/the-ruby-on-rails-way-for-model-naming/#comment-112</guid>
		<description><![CDATA[If it&#039;s just the date (ie day resolution) that&#039;s important then this looks fine. If you&#039;d like the time as well, use eg delivered_at.

By primary field do you meant the primary key? If so, it should always be an auto-incrementing integer ID.

Write your tests first or I&#039;ll have to beat you ;)]]></description>
		<content:encoded><![CDATA[<p>If it&#8217;s just the date (ie day resolution) that&#8217;s important then this looks fine. If you&#8217;d like the time as well, use eg delivered_at.</p>
<p>By primary field do you meant the primary key? If so, it should always be an auto-incrementing integer ID.</p>
<p>Write your tests first or I&#8217;ll have to beat you <img src='http://s1.wp.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

