Subject | Re: [firebird-support] Translation strings for web application in Firebird |
---|---|
Author | Hannes Streicher |
Post date | 2004-03-03T12:57:48Z |
Guten Tag h_urlaf,
am Mittwoch, 3. März 2004 um 10:25 schrieben Sie:
h> We're writing a multi-language ASP web application, which stores the
h> translated texts in a windows resource DLL so far. Now, a client wants
h> different users to be able to select their preferred translation
h> separately, so since we're migrating to FB anyway I was thinking about
h> storing these translated texts in a database and pull them from there
h> at page generation time. This means FB would see a quite large number
h> of requests per page visit to this table. The table would look
h> something like this:
h> CREATE TABLE TRANSLATIONS
h> (
h> LOCALE_ID INTEGER NOT NULL,
h> TRANSLATION_ID BIGINT NOT NULL,
h> TRANSLATION_TEXT VARCHAR(1024) NOT NULL,
h> PRIMARY KEY (LOCALE_ID, TRANSLATION_ID),
h> );
h> My questions:
h> * Is this a reasonable use for FB? Are other people doing things like
h> this?
similar , i use the ISO alpha 2 Codes for language coding , however i
do not use fb on this , and why do you need a Bigint for the
Translation ID , a 32 Bit Integer with 4 Billion Sentences shud keep
you typing translations for the rest of your life :)
--
Mit freundlichen Grüssen / with best regards
Hannes Streicher mailto:HStreicher@...
am Mittwoch, 3. März 2004 um 10:25 schrieben Sie:
h> We're writing a multi-language ASP web application, which stores the
h> translated texts in a windows resource DLL so far. Now, a client wants
h> different users to be able to select their preferred translation
h> separately, so since we're migrating to FB anyway I was thinking about
h> storing these translated texts in a database and pull them from there
h> at page generation time. This means FB would see a quite large number
h> of requests per page visit to this table. The table would look
h> something like this:
h> CREATE TABLE TRANSLATIONS
h> (
h> LOCALE_ID INTEGER NOT NULL,
h> TRANSLATION_ID BIGINT NOT NULL,
h> TRANSLATION_TEXT VARCHAR(1024) NOT NULL,
h> PRIMARY KEY (LOCALE_ID, TRANSLATION_ID),
h> );
h> My questions:
h> * Is this a reasonable use for FB? Are other people doing things like
h> this?
similar , i use the ISO alpha 2 Codes for language coding , however i
do not use fb on this , and why do you need a Bigint for the
Translation ID , a 32 Bit Integer with 4 Billion Sentences shud keep
you typing translations for the rest of your life :)
--
Mit freundlichen Grüssen / with best regards
Hannes Streicher mailto:HStreicher@...