<?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: Introducing Envers: Easy Entity Versioning</title>
	<atom:link href="http://www.warski.org/blog/?feed=rss2&#038;p=8" rel="self" type="application/rss+xml" />
	<link>http://www.warski.org/blog/?p=8</link>
	<description>Java and JBoss related stuff</description>
	<lastBuildDate>Wed, 01 Sep 2010 16:45:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Adam Warski</title>
		<link>http://www.warski.org/blog/?p=8&#038;cpage=1#comment-502</link>
		<dc:creator>Adam Warski</dc:creator>
		<pubDate>Fri, 11 Apr 2008 07:21:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.warski.org/blog/?p=8#comment-502</guid>
		<description>Now that you mention it, sure. I didn&#039;t plan it before, but, as I wrote - I&#039;d like to know what would be useful to possible users, like you. Storing all data in one table seems a really good idea :). Thanks!</description>
		<content:encoded><![CDATA[<p>Now that you mention it, sure. I didn&#8217;t plan it before, but, as I wrote &#8211; I&#8217;d like to know what would be useful to possible users, like you. Storing all data in one table seems a really good idea :). Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tech Per</title>
		<link>http://www.warski.org/blog/?p=8&#038;cpage=1#comment-501</link>
		<dc:creator>Tech Per</dc:creator>
		<pubDate>Thu, 10 Apr 2008 19:17:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.warski.org/blog/?p=8#comment-501</guid>
		<description>This is a *great* idea.

There are various ways to do historical data, and I have used the one with a separate table as envers do too. But you can also choose to store historical data in the same table, using validFrom and validTo timestamp columns, to mark entries as historical. I am sure, there are other ways. Is there anything in the plans or thoughts, to support alternative ways, to store the historical data?</description>
		<content:encoded><![CDATA[<p>This is a *great* idea.</p>
<p>There are various ways to do historical data, and I have used the one with a separate table as envers do too. But you can also choose to store historical data in the same table, using validFrom and validTo timestamp columns, to mark entries as historical. I am sure, there are other ways. Is there anything in the plans or thoughts, to support alternative ways, to store the historical data?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
