Hi Vincent, > In my case $msg.get would have to request the message from the database > on the basis of the message. Suppose (which is not at all unlikely in my > situation) that we're talking about a database with 250.000 products. > Each product has mutliple internationalized texts (description, title, > etc...) , even with only two messages per product this would result in > 500.000 entries. It would not be convinient to create a code to message > mapping. Showing just a list of search results would be an huge strain > on the database. The objects themselves would need to know their > messages in different languages, that would be more convinient.
All the localized text is in the database, right? How about getting the localized text prior to setting it in the Context? Best regards, -- Shinobu Kawai -- Shinobu Kawai <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
