class I18n::Backend::KeyValue

This is useful if you are using a KeyValue backend chained to a Simple backend.
I18n::Backend::KeyValue.new(@store, false)
allowed to disable the storage of subtrees on initialization:
of new data considerably and makes hard to delete entries. That said, you are
This backend supports this feature by default, but it slows down the storage
I18n.t “foo” #=> { :bar => :baz }
I18n.backend.store_translations :en, :foo => { :bar => :baz }
In most backends, you are allowed to retrieve part of a translation tree:
== Subtrees
values directly in the key-store.
However, notice that you should properly clear the cache if you change
You may make this backend even faster by including the Memoize module.
== Performance
I18n.backend = I18n::Backend::KeyValue.new(Rufus::Tokyo::Cabinet.new(‘*’))
require ‘rufus/tokyo/cabinet’ # gem install rufus-tokyo
To setup I18n to use TokyoCabinet in memory is quite straightforward:
== Example
expensive operation in most stores.
Also, avoid calling I18n.available_locales since it’s a somehow
translations from the filesystem or through explicit store translations.
As the ActiveRecord backend, Symbols are just supported when loading
hashes and arrays. However, this store does not support Procs.
to JSON before being stored, allowing it to also store booleans,
Since these stores only supports string, all values are converted
* store#keys - Used to get all keys
* store#[]=(key, value) - Used to set a value
* store#[](key) - Used to get a value
initialization the store, which should respond to three methods:
This is a basic backend for key value stores. It receives on