discourse-translator/db/migrate
Alan Guo Xiang Tan 5e833a80ad
DEV: Rerun CreateTranslationIndexes migration (#251)
The previous version of the migration is not idempotent and can result
in indexes created but marked as "invalid" by Postgres.

Per postgres documentation:

If a problem arises while scanning the table, such as a deadlock or a
uniqueness violation in a unique index,
the CREATE INDEX command will fail but leave behind an "invalid" index.
This index will be ignored for querying
purposes because it might be incomplete; however it will still consume
update overhead. The recommended recovery
  method in such cases is to drop the index and try again to perform
  CREATE INDEX CONCURRENTLY.
2025-03-14 09:39:10 +08:00
..
20210429154318_remove_empty_translation_custom_fields.rb DEV: Promote historic post_deploy migrations (#91) 2022-12-19 17:27:43 +02:00
20230323110557_rename_translator_azure_custom_domain_site_setting.rb DEV: Rename translator_azure_custom_domain Site Setting (#102) 2023-04-17 14:07:23 +00:00
20250205082400_create_translation_tables.rb DEV: Move translation custom fields into their own tables (#201) 2025-02-10 12:29:07 +08:00
20250205082401_move_translations_custom_fields_to_table.rb DEV: Move translation custom fields into their own tables (#201) 2025-02-10 12:29:07 +08:00
20250210171147_hyphenate_translator_locales.rb DEV: Hyphenate locales (#206) 2025-02-11 16:04:22 +08:00
20250224120505_cleanup_ai_translations.rb FIX: Do not return AI content if not in <output> (#223) 2025-02-25 10:53:57 +08:00
20250227074505_rename_translator_site_settings.rb DEV: Cleanup terms (#232) 2025-02-27 17:40:56 +08:00
20250313082243_create_translation_indexes.rb DEV: Rerun CreateTranslationIndexes migration (#251) 2025-03-14 09:39:10 +08:00