<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for pteli</title><link>http://disqus.com/by/pteli/</link><description></description><atom:link href="http://disqus.com/pteli/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 16 Jul 2009 19:28:51 -0000</lastBuildDate><item><title>Re: Tomash corner

/ Migrating to Rails 2.3 and Globalize2 from Rails 2.1 and Globalize1</title><link>http://tomash.wrug.eu/2009/06/01/migrating-to-rails-2-3-with-globalize.html#comment-12777497</link><description>&lt;p&gt;Thanks for the article. I have a question.&lt;br&gt;Do you know if Globalize2 gives an option of storing the translation columns in the same model instead of keeping them in a separate table? I am running into a performance issue when the number of entries in the model table grows, the # of join queries increases as well.&lt;/p&gt;&lt;p&gt;I saw an article by Simon Moore at&lt;br&gt;&lt;a href="http://saimonmoore.net/2006/12/1/alternative-implementation-of-globalize-model-translations" rel="nofollow noopener" target="_blank" title="http://saimonmoore.net/2006/12/1/alternative-implementation-of-globalize-model-translations"&gt;http://saimonmoore.net/2006...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;That talks about storing all your translations along with the original model.&lt;/p&gt;&lt;p&gt;Will this work with Globalize2?&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pteli</dc:creator><pubDate>Thu, 16 Jul 2009 19:28:51 -0000</pubDate></item></channel></rss>