<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
 
 <title>rubyrep blog</title>
 <link href="http://www.rubyrep.org/atom.xml" rel="self"/>
 <link href="http://www.rubyrep.org/"/>
 <updated>2010-02-03T02:10:50-08:00</updated>
 <id>http://www.rubyrep.org/</id>
 <author>
   <name>Arndt Lehmann</name>
   <email>arndt@arndtlehmann.com</email>
 </author>
 
 
 <entry>
   <title>rubyrep version 1.0.6 released</title>
   <link href="http://www.rubyrep.org/2009/07/25/version-1.0.6-released.html"/>
   <updated>2009-07-25T00:00:00-07:00</updated>
   <id>http://www.rubyrep.org/2009/07/25/version-1.0.6-released</id>
   <content type="html">&lt;p&gt;Quick update: I have released version 1.0.6 of rubyrep.&lt;br /&gt;
Changes:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Bug fix: rubyrep does not assume anymore that replication events appear in the &lt;code&gt;rr_pending_changes&lt;/code&gt; table in sequential order.&lt;br /&gt;
  (This could lead to some changes being left behind and only getting picked up after a replication restart.)&lt;/li&gt;
	&lt;li&gt;Feature: the replication daemon is now more resilient towards network timeouts.&lt;br /&gt;
  (I. e. less likely to get stuck.)&lt;/li&gt;
	&lt;li&gt;Feature: introduction of an &lt;code&gt;:after_infrastructure_setup&lt;/code&gt; handler that allows users to execute custom code after infrastructure tables are created.&lt;br /&gt;
  (Useful to e. g. grant additional database users access to the &lt;code&gt;rr_pending_changes&lt;/code&gt; table.)&lt;/li&gt;
&lt;/ul&gt;</content>
 </entry>
 
 <entry>
   <title>rubyrep version 1.0.4 released</title>
   <link href="http://www.rubyrep.org/2009/06/22/version-1.0.4-released.html"/>
   <updated>2009-06-22T00:00:00-07:00</updated>
   <id>http://www.rubyrep.org/2009/06/22/version-1.0.4-released</id>
   <content type="html">&lt;p&gt;Quick update: I have released version 1.0.4 of rubyrep.&lt;br /&gt;
Changes:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Support for esoteric table and column names (e. g. with non-&lt;span class=&quot;caps&quot;&gt;ASCII&lt;/span&gt; or mixed-case characters)&lt;/li&gt;
	&lt;li&gt;The rubyrep JRuby version is now bundled wit JRuby 1.3.0&lt;/li&gt;
&lt;/ul&gt;</content>
 </entry>
 
 <entry>
   <title>Battle tested</title>
   <link href="http://www.rubyrep.org/2009/06/14/battle-tested.html"/>
   <updated>2009-06-14T00:00:00-07:00</updated>
   <id>http://www.rubyrep.org/2009/06/14/battle-tested</id>
   <content type="html">&lt;p&gt;I have been using rubyrep for one of our production applications since April. Another one just went online on Friday.&lt;br /&gt;
So having fulfilled the definition of the word, I hereby declare rubyrep &lt;strong&gt;battle tested&lt;/strong&gt;.&lt;/p&gt;</content>
 </entry>
 
 <entry>
   <title>Initial release</title>
   <link href="http://www.rubyrep.org/2009/03/08/initial-release.html"/>
   <updated>2009-03-08T00:00:00-08:00</updated>
   <id>http://www.rubyrep.org/2009/03/08/initial-release</id>
   <content type="html">&lt;p&gt;It took more than one year and a half. But here it finally is. An open source solution for ridiculously easy setup of master-master replication of releational databases.&lt;/p&gt;
&lt;p&gt;Want to see how to set up replication in under 5 minutes? Head to the &lt;a href=&quot;screencast.html&quot;&gt;screencast&lt;/a&gt;. Enjoy.&lt;/p&gt;</content>
 </entry>
 
 
</feed>

