How we've migrated from globalize to hstore-translate

Description and use

Migrated from globalize to hstore-translate, reducing the number of database tables and simplifying the translation schema.

Problem

The application used the globalize gem for translations, which stores translations in separate database tables and requires manual schema management.

Outcome

Successfully migrated from globalize to hstore-translate, reducing the number of database tables and simplifying the translation schema.

Workflow

• Identify all models that used globalize for translations.
• Replace globalize with hstore-translate gem.
• Update the database schema to use hstore columns instead of globalize tables.
• Migrate existing translation data from globalize tables to hstore columns.
• Verify that all translations are correctly stored and accessible.

Evidence

How we've migrated from globalize to hstore-translate