| | |
Need help in designing some tables
Please support our Database Design advertiser: PostgreSQL or MySQL? Compare and contrast the two most popular open source databases
![]() |
•
•
Join Date: Jan 2009
Posts: 3
Reputation:
Solved Threads: 0
I thougt of 2 possibilites:
Possibility 1.
Table 1: French vocabulary
Table 2: English vocabulary
Table 3: Translation table containing primary keys of table 1 and 2
Possibility 2.
French vocabulary and English vocabulary in one table where the French and English fields contain one or more vocables delimited by a ';'
Is there another possibility I haven't thought of?
Thanks in advance.
Regards,
DBGuy007
Possibility 1.
Table 1: French vocabulary
Table 2: English vocabulary
Table 3: Translation table containing primary keys of table 1 and 2
Possibility 2.
French vocabulary and English vocabulary in one table where the French and English fields contain one or more vocables delimited by a ';'
Is there another possibility I haven't thought of?
Thanks in advance.
Regards,
DBGuy007
•
•
Join Date: Aug 2007
Posts: 165
Reputation:
Solved Threads: 18
Considering that translation/interpretation is usually one-to-many, you might be better off with option 1, where you have your vocabularies cleanly stored in the two language tables and your third table defines the relation (translation/interpretation) between the languages. This would also make it easier (in a manner of speaking) to add more languages.
•
•
Join Date: Apr 2008
Posts: 296
Reputation:
Solved Threads: 42
Hi, I am back again.
Because of "A French vocable got one or more English vocable equivalents and vice versa." there exists a many-to-many relationship between both entities. Therefore this is the correct solution:
Possibility 2 is highly erroneous because it violates first normal form, creates anomalies, does not allow to creating effective sql- queries. It topsy-turvifys Codd's relational theory completely.
-- tesu
Because of "A French vocable got one or more English vocable equivalents and vice versa." there exists a many-to-many relationship between both entities. Therefore this is the correct solution:
•
•
•
•
Possibility 1.
Table 1: French vocabulary
Table 2: English vocabulary
Table 3: Translation table containing primary keys of table 1 and 2
DBGuy007
-- tesu
Information is moving—you know, nightly news is one way, of course, but it's also moving through the blogosphere and through the Internets. I promise you I will listen to what has been said here, even though I wasn't here. Ann and I will carry out this equivocal message to the world. I'm the master of low expectations.
![]() |
Similar Threads
- Please review my mortgage site redesign (Website Reviews)
- Why do people wish for tableless with CSS? (HTML and CSS)
- Database design regarding two 'linking' tables (Database Design)
- retrive data from different tables of Ms access (ASP)
- retrive data from different tables of Ms access (ASP)
- Trying to use not tables, only CSS, but can I? (HTML and CSS)
- Browser Compatibility Problems (HTML and CSS)
- designing with em / ex ? (HTML and CSS)
Other Threads in the Database Design Forum
- Previous Thread: "Common" tables
- Next Thread: Can you help me pick out the remaning entity to finsish the ERD.
| Thread Tools | Search this Thread |






