> Judith, perhaps one thing that will help you out is to know that in  
> fact the globalize translations table can use anything you like for  
> a key. While all of the examples are complete English phrases it  
> does not have to be used that way. You can readily use a shorthand  
> encoding mechanism for each message and that will index (and  
> therefore be looked up) much faster than long phrases.
>
> Note: if you do this then you will have to add "translations" for  
> the English text in addition to other languages. Then the  
> "translated" English will show up in place of the "keyword" English  
> text.
>
> Dan
>
> Judith Meyer wrote:
>> Hello,
>>
>> I still haven't got an answer, even though I wrote to this list
>> several weeks ago. I want to let you know that I'm really worried
>> about scalability - I'm programming a really big social network and
>> I'm very worried about how this will scale, seeing that texts from  
>> the
>> views in the database are identified by the English texts rather than
>> an id or something more searchable. If nobody can reassure me or give
>> me an example of a really popular website that successfully uses
>> Globalize, I will do a major fork / re-write for my company. We just
>> can't risk having to re-code this when translations refuse to scale  
>> to
>> keep up with our growth of users.
>>
>> Best regards,
>>
>> Judith Meyer
>>
>>
>>
>