embedded_localization 0.1.4 → 0.2.0

data/README.textile

@@ -50,15 +50,28 @@ g.name  # => "공상 과학 소설"
 
 No extra tables needed for this!
 
-h3. Rails 3.0 + Embedded_Localization version < 0.2.0
+h3. Rails 3.0
 
 <pre><code>
 class CreateGenres < ActiveRecord::Migration
   def self.up
     create_table :genres do |t|
-      t.text   :i18n    # this will be deprecated in 0.2.0
+      t.text   :i18n    # stores the translated attributes; persisted as a HashWithIndifferentAccess
+
+# optional:
+#      t.string :name    # you CAN define :name as a real column in your DB (but you don't have to)
+#                        # If you define it, it will store the I18n.default_locale translation for SQL lookups
+#                        # You can do this for any of the translated attributes.
       t.timestamps
     end
+    # -- example for a data migration: ---
+    # Genre.record_timestamps = false
+    # Genre.all.each do |g|
+    #   g.name = g.name   # the right-hand-side fetches the translation from the i18n attribute hash
+    #   g.save            # saves the :name attribute without updating the updated_at timestamp
+    # end
+    # Genre.record_timestamps = true
+    # ------------------------------------
   end
   def self.down
     drop_table :posts
@@ -66,7 +79,16 @@ class CreateGenres < ActiveRecord::Migration
 end
 </code></pre>
 
-Please note, if you use Embedded_Localization with version < 0.2.0, that you should not define the translated attributes in the migrations -- instead define one text attribute with the name :i18n -- this will change in version 0.2.0
+h4. NOTE:
+
+EmbeddedLocalization implementations < 0.2.0 have the drawback that you can not do SQL queries on translated attributes.
+
+To eliminate this limitation, you can now define any translated attribute as a first-class database column in your migration. If you define a translated attribute as a column, EmbeddedLocalization will store the attribute value for I18n.default_locale in that column, so you can search for it. After defining the column, and running the migration, you need to populate the column initially. It will auto-update every time you write while you are using I18n.default_locale .
+e.g.:
+
+<pre><code>
+  g = Genre.where(:name => "science fiction")   # this only works if you define :name as a DB column, and populate it
+</pre></code>
 
 Note that the ActiveRecord model @Genre@ must already exist and have a @translates@ directive listing the translated fields.
 

data/lib/embedded_localization/active_record/act_macro.rb

@@ -68,6 +68,9 @@ module EmbeddedLocalization
             #
             define_method(attr_name.to_s+ '=') do |new_translation|
               self.i18n_will_change!     # for ActiveModel Dirty tracking
+              if self.attributes.has_key?(attr_name.to_s)  # if user has defined DB field with that name
+                write_attribute(attr_name , new_translation) if I18n.locale == I18n.default_locale
+              end
               self.i18n[I18n.locale] ||= HashWithIndifferentAccess.new
               self.i18n[I18n.locale][attr_name] = new_translation
             end

data/lib/embedded_localization/active_record/instance_methods.rb

@@ -18,6 +18,9 @@ module EmbeddedLocalization
       
       def set_localized_attribute(attr_name, locale, new_translation)
         self.i18n_will_change!     # for ActiveModel Dirty tracking
+        if self.attributes.has_key?(attr_name.to_s)  # if user has defined DB field with that name
+          write_attribute(attr_name , new_translation) if locale == I18n.default_locale
+        end
         self.i18n[locale] ||= HashWithIndifferentAccess.new
         self.i18n[locale][attr_name] = new_translation
       end

data/lib/embedded_localization/version.rb

@@ -1,3 +1,3 @@
 module EmbeddedLocalization
-  VERSION = '0.1.4'
+  VERSION = '0.2.0'
 end

metadata

@@ -2,7 +2,7 @@
 name: embedded_localization
 version: !ruby/object:Gem::Version 
   prerelease: 
-  version: 0.1.4
+  version: 0.2.0
 platform: ruby
 authors: 
 - Tilo Sloboda