Simple Table Design Question

[dataminers]

Dictionary Table; Records in only 2 lines (for example, a table of sex: male, female) or as much as 40-50 lines and changing of future data in the table Insert / Update / Delete operations possibility of very low.

Combining these tables in a single table, Does it make sense?

For Example;

TBL_Sex
1 Male
2 Female

TBL_WorkType
1 Full-Time
2 Part-Time

TBL_BloodType
1 A Rh(+)
2 B Rh(+)
3 AB Rh(+)
4 0 Rh(-)
5 A Rh(-)
6 B Rh(-)
7 AB Rh(-)
8 0 Rh(-)

Instead of following table;

TBL_DICTIONARY

ID GROUP VALUE

---

1 Sex Erkek
2 Sex Kadın
3 WorkType Yarım Gün
4 WorkType Tam Gün
5 BloodType A Rh(+)
6 BloodType B Rh(+)
7 BloodType AB Rh(+)
8 BloodType 0 Rh(-)
9 BloodType A Rh(-)
10 BloodType B Rh(-)
11 BloodType AB Rh(-)
12 BloodType 0 Rh(-)

[Luc Pattyn]

I'd use separate tables for such "enums". :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]

---

I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.
[The QA section does it automatically now, I hope we soon get it on regular forums as well]

---

[dataminers]

So; Do you use TBL_Sex, TBL_WorkType, TBL_BloodType or use TBL_DICTIONARY ?

[Andy_L_J]

dataminers wrote:

use TBL_Sex, TBL_WorkType, TBL_BloodType

:thumbsup:

I don't speak Idiot - please talk slowly and clearly 'This space for rent' Driven to the arms of Heineken by the wife

[David Mujica]

Using separate tables also allows you to create foreign key references so that you can guarantee that the data in your tables remain consistent. For example: Tbl_Patient ID: Sex: Work_type: Blood_type: additional fields, blah, blah ... On this new table,Tbl_Patient, you would create foreign key references to tbl_sex, tbl_worktype, tbl_bloodtype, so that only valid values can be stored in those columns. Good luck on your project and keep asking questions ... it's the only way to learn. :cool: