I suppose that this is more of an application design question than a Turbine question, but wouldn't it be easier to normalize the product name and language in another localization info table and link back to a product table?
PRODUCT ID | <other things about the product, like price etc.>
PRODUCT_L10N_INFO PRODUCT_ID (foreign key to PRODUCT) | LOCALE | KEY | VALUE
This way, you could just get the locale from the RunData or from the e-shop configuration (wherever that is) and include it as part of your Torque criteria. No need to get into caching. Just a thought.
-Brian
On Apr 7, 2004, at 12:15 AM, Niki Ivanchev wrote:
Hi all.
I have this problem. I am designing a e-shop /with admin part and csutomer part/
I am totaly using turbine/velocity/torque.
e-shop must support several languages /let's say 10, may be more/
E-shop owner decides which languages to use.
When desigining database, I can add column per lanugage /for example product_name_en, product_name_fr, product_name_de etc./
Or I can add product_names as BLOB and use XML. My problem is that each time I have to marshal/unmarshal XML's into java objects
So I decided to put those into cache. But in doc's cache have default time of 5 sec. So may be it is designed to keep other data in it.
I forgot to mention that the server must hold at lease 100 e-shops togather with their databases /probably will bet on firebird/
Any advice on shall I bet on caching service to keep away from marshaling/unmarshaling is welcome
Regards
Niki
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
