MailingList


 « Return to Thread: caching of default view translations

caching of default view translations

by Nicola Piccinini :: Rate this Message:

Reply to Author | View in Thread

Hi,

I noticed that default view translations were killing the db because
they were not cached so I changed this behavior
( http://github.com/pic/globalize/commit/669fa2762e8dbb1bdaddef583158901a8d1328d4
)

Now I'm wondering if there is any side effect, are there any reasons
to keep default translations out of cache?

Recently Judith Meyer suggested to completely avoid to hit the db for
default translations:
http://www.nabble.com/Re%3A-globalize_translations-table-p17272887s17045.html

This is a good point but I still prefer to have a chance to translate
even the default because sometimes they are "symbols" (not in Ruby
sense).

Any thought?
Thanks,

Nicola

 « Return to Thread: caching of default view translations