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
$this->Person->findByFirstName('Pär');
which in Swedish should return users that are called just that but in
English should return any name with any variation of the a character
since ä is not a character in the English alphabet. It is only seen as
an a with some irrelevant "bling bling".
I have not seen any supported way of telling the database which
language you want to search in. All I have know of is to try to hack
it into the conditions and order clauses and end up just one step
short of a custom query.
Using separate tables you at least have the option to set them to the
correct collation for the intended language.
Sorry for taking up space with this explanation. It ran a bit long but
it can be unpleasant finding out your searches return the wrong data
when your app is already live. :) I hope someone with good experience
using the translate behaviour can shed some light on how they get make
it work.
On Sep 22, 6:33 pm, chrispie <[email protected]> wrote:
> 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!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
