discourse/db/migrate/20140624044600_add_raw_data...

# frozen_string_literal: true

class AddRawDataToSearch < ActiveRecord::Migration[4.2]
  def change
    add_column :post_search_data, :raw_data, :text
    add_column :user_search_data, :raw_data, :text
    add_column :category_search_data, :raw_data, :text

    add_column :post_search_data, :locale, :string
    add_column :user_search_data, :locale, :text
    add_column :category_search_data, :locale, :text
  end
end
DEV: enable frozen string literal on all files This reduces chances of errors where consumers of strings mutate inputs and reduces memory usage of the app. Test suite passes now, but there may be some stuff left, so we will run a few sites on a branch prior to merging 2019-05-02 18:17:27 -04:00			`# frozen_string_literal: true`

Fix all the errors to get our tests green on Rails 5.1. 2017-08-31 00:06:56 -04:00			`class AddRawDataToSearch < ActiveRecord::Migration[4.2]`
BUGFIX: Chinese search was broken BUGFIX: User locale was used index data BUGFIX: missing Norwegian fulltext config FEATURE: store the text used to index stuff in fulltext (for diagnostics / in page search) FEATURE: re-index posts when locale changes (in bg job) FEATURE: allow reindexing by trucating post_search_data Note: I removed japanese specific config cause it requires custom pg config, happy to add it once our base docker config ships with it 2014-06-24 03:10:56 -04:00			`def change`
			`add_column :post_search_data, :raw_data, :text`
			`add_column :user_search_data, :raw_data, :text`
			`add_column :category_search_data, :raw_data, :text`

			`add_column :post_search_data, :locale, :string`
			`add_column :user_search_data, :locale, :text`
			`add_column :category_search_data, :locale, :text`
			`end`
			`end`