One thing I have yet to figure out is how to deal with charset/
collation problems using an i18n table. Because of this I would
probably go for separate tables even though it requires more work to
make id's sync and all that.
The problems I am referring to are queries like
hei list!
I was wondering if the i18n table is still state of the art for about
30 000 entrys (cities) in a model (=180 000 entrys in i18n).
Or is there a better solution like using a table prefix for different
languages (de_cities, en_cities,)?
thankYouVeryMuch
chris!
