You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering how to migrate existing data to the jsonb?
My existing schema for an application as setup with title and content However, after a decision to make the content available internationally, we decided to incorporate a translation gem.
The problem here is that the values originally stored in title are no longer accessible. I can only access them when I comment out the translates :title, :content line at the top of the model, which means I can't do it via simple script.
I think one simple solution to this would be to give users of the gem the ability to turn the translation on/off similar to how easy you made it to do i18n fallbacks on/off. That way at least users can write a simple script to migrate existing values.
The text was updated successfully, but these errors were encountered:
I was wondering how to migrate existing data to the jsonb?
My existing schema for an application as setup with
title
andcontent
However, after a decision to make the content available internationally, we decided to incorporate a translation gem.Here is the result:
The problem here is that the values originally stored in title are no longer accessible. I can only access them when I comment out the
translates :title, :content
line at the top of the model, which means I can't do it via simple script.I think one simple solution to this would be to give users of the gem the ability to turn the translation on/off similar to how easy you made it to do i18n fallbacks on/off. That way at least users can write a simple script to migrate existing values.
The text was updated successfully, but these errors were encountered: