<?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: Business and Application Logic, Part 2</title>
	<atom:link href="http://www.tarkblog.org/general/228/feed" rel="self" type="application/rss+xml" />
	<link>http://www.tarkblog.org/general/228</link>
	<description>The personal writings of Caleb and Annie Tennis</description>
	<pubDate>Wed, 07 Jan 2009 04:54:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Bean</title>
		<link>http://www.tarkblog.org/general/228#comment-493</link>
		<dc:creator>Bean</dc:creator>
		<pubDate>Tue, 29 Nov 2005 13:53:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.tarkblog.org/?p=228#comment-493</guid>
		<description>'has_many_needs_most_recent' sounds a whole lot like 'order by date desc limit 1'.

I deal a lot with employee records and dynamic data, and the way we keep it all straight is to completely abstract the employees information and assign them a Personal ID or PID (employee_id in your case).  Names change, SSN's are entered wrong, etc.  PID allows me to keep it all linked.</description>
		<content:encoded><![CDATA[<p>&#8216;has_many_needs_most_recent&#8217; sounds a whole lot like &#8216;order by date desc limit 1&#8242;.</p>
<p>I deal a lot with employee records and dynamic data, and the way we keep it all straight is to completely abstract the employees information and assign them a Personal ID or PID (employee_id in your case).  Names change, SSN&#8217;s are entered wrong, etc.  PID allows me to keep it all linked.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
