How to create a dictionary using relations ?

From: Claude Vernier (ClaudeVernier_at_discussions.microsoft.com)
Date: 01/19/05


Date: Wed, 19 Jan 2005 07:39:05 -0800


Hi,

I must admit, I don't what MSEQ means... I have a business need I want to
implement in my database and don't know how. I nice fellow from
sqlserver.olap suggested me to come here...

I want to create a dictionary. For me, this a table that would contain any
string
I need to show in several languages and I can't find the best way to create
my
tables and the relations I should use... I need help.

Here's what I have:

Table: Queries
Column: ID, int, 4
Column: Text, varchar, 50
Column: DictionaryID_Name, int, 4
Sample:
---------------------------------------------
| ID | Text | DictionaryID_Name |
---------------------------------------------
| 1 | [xml] | 1 |
| 2 | [xml] | 2 |
---------------------------------------------

Table: Formattings
Column: ID, int, 4
Column: Text, varchar, 50
Column: DictionaryID_Name, int, 4
Sample:
---------------------------------------------
| ID | Text | DictionaryID_Name |
---------------------------------------------
| 1 | [xml] | 3 |
| 2 | [xml] | 4 |
---------------------------------------------

Table: Languages
Column: ID, int, 4
Column: Text, varchar, 50
Sample:
---------------------
| ID | Text |
---------------------
| 1 | English |
| 2 | French |
---------------------

Table: Dictionary
Column: ID, int, 4
Column: Text, varchar, 50
Column: LanguagesID_Name, int, 4
Sample:
---------------------------------------------
| ID | Text | LanguagesID_Name |
---------------------------------------------
| 1 | Txt for Q1 | 1 |
| 1 | Txt for Q1 | 2 |
| 2 | Txt for Q2 | 1 |
| 2 | Txt for Q2 | 2 |
| 3 | Txt for F1 | 1 |
| 3 | Txt for F1 | 2 |
| 4 | Txt for F2 | 1 |
| 4 | Txt for F2 | 2 |
---------------------------------------------

As you can see, Dictionary would contain a version of each string for
each supported language in Languages. The problem is, I can't make a relation
between (Queries or Formattings) and Dictionary.

I don't know if this is a typical problem, but I just realized my
implementation does not work.
If someone could help with any suggestion on this type of database... thanks
you very much



Relevant Pages