Currently only the translated keys are being cached, those that have no
translation are not.
I believe a form of caching should be done for the keys/strings that do not
have (yet) a translation, because right now the application keeps trying to
find a translation that is not there.
A mundane way would be to cache a predefined value for strings that did not
have a translation, and return the original sentence (without trying to
fetch the translation from the DB)
I would guess that something like ''-=+-;+_'' would be safe
enough ;)
When a translation is added for a key, the previous version (the predefined
value) is removed anyway, so the only problem would appear when
globalize_translations table is populated from outside the application. But
in that case a refresh_cache_for_desired_values method could be added and be
run whenever desired.
I have an application that has many thousands strings that will have to be
translated, and having globalize endlessly trying to pull translations from
the DB for strings that have no translation would kill it.
bogdan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060914/d23daa33/attachment-0001.html
