README.md in fuzzily-0.3.2 vs README.md in fuzzily-0.3.3

- old
+ new

@@ -13,11 +13,11 @@ Fuzzily finds misspelled, prefix, or partial needles in a haystack of strings. It's a fast, [trigram](http://en.wikipedia.org/wiki/N-gram)-based, database-backed [fuzzy](http://en.wikipedia.org/wiki/Approximate_string_matching) string search/match engine for Rails. Loosely inspired from an [old blog post](http://unirec.blogspot.co.uk/2007/12/live-fuzzy-search-using-n-grams-in.html). -Tested with ActiveRecord (2.3, 3.0, 3.1, 3.2, 4.0) on various Rubies (1.8.7, 1.9.2, 1.9.3, 2.0.0) and the most common adapters (SQLite3, MySQL, and PostgreSQL). +Tested with ActiveRecord (2.3, 3.0, 3.1, 3.2, 4.0) on various Rubies (1.8.7, 1.9.3, 2.0.0, 2.1.0) and the most common adapters (SQLite3, MySQL, and PostgreSQL). If your dateset is big, if you need yet more speed, or do not use ActiveRecord, check out [blurrily](http://github.com/mezis/blurrily), another gem (backed with a C extension) with the same intent. @@ -164,10 +164,19 @@ first_name_changed? || last_name_changed? end end ``` +## Update Trigram index using `sidekiq-delay` +For larger text, it takes time to build the index. Thus it can be moved into delay task using `sidekiq` + `sidekiq-delay` or `delayed_job` gem, both of them provide the method `delay` to move the execution to background thread by adding option `async`: + +```ruby +class Employee < ActiveRecord::Base + fuzzily_searchable :name, async: true + +end +``` ## License MIT licence. Quite permissive if you ask me.