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 want to create indexes to improve the speed of searches, but I read in the readme that by using the unaccent extension you can not use the function that gives the default extension.
"Advanced users may wish to add indexes for the expressions that pg_search generates. Unfortunately, the unaccent function supplied by this extension is not indexable (as of PostgreSQL 9.1). Thus, you may want to write your own wrapper function and use it instead. This can be configured by calling the following code, perhaps in an initializer."
PgSearch.unaccent_function = "my_unaccent"
Then I have to make a wrapper function, but it is not clear to me how this could be.
I imagine that it is necessary to execute some migration that creates a function? How would that be? Is it necessary to change the schema to SQL?
Maybe it would also be good to add an example to the readme or to the wiki.
Does this limitation still exist in Postgres 14?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi, thanks for this amazing gem!
I want to create indexes to improve the speed of searches, but I read in the readme that by using the unaccent extension you can not use the function that gives the default extension.
"Advanced users may wish to add indexes for the expressions that pg_search generates. Unfortunately, the unaccent function supplied by this extension is not indexable (as of PostgreSQL 9.1). Thus, you may want to write your own wrapper function and use it instead. This can be configured by calling the following code, perhaps in an initializer."
PgSearch.unaccent_function = "my_unaccent"
Then I have to make a wrapper function, but it is not clear to me how this could be.
I imagine that it is necessary to execute some migration that creates a function? How would that be? Is it necessary to change the schema to SQL?
Maybe it would also be good to add an example to the readme or to the wiki.
Does this limitation still exist in Postgres 14?
Thanks!
The text was updated successfully, but these errors were encountered: