Database Design
Akopọ
Nobody ever writes a database twice. The design decisions made in the first hour, which tables exist, what each field holds and which field identifies a record, are the ones everything afterwards is built on, and they are the ones that are painful to change once there is real data in the system. Getting them right is a skill, and it is a skill made of three specific choices rather than of general good taste.
This lesson teaches those three choices: picking an appropriate data type, and a length where a length is called for; selecting a suitable primary key; and turning a paragraph describing a situation into a set of linked tables. You will also learn the exact notation this specification uses to write a design down, which is worth knowing precisely, because a design written in the expected form is quick to mark and a design sketched informally is not.
Awọn Afojusun
- Be able to choose appropriate data types and (where appropriate) lengths for fields in a table. Be able to select a suitable primary key for a table. Be able to produce a design for a relational database from a description of a scenario.
Àwòrán ọpọlọ
A ti ṣe àwòrán kókó yìí kí o lè rí bí àwọn èrò ṣe so pọ̀.
Ṣí àwòrán ọpọlọ nínú áàpù
Akọ̀wé Ẹ̀kọ́
Àkọsílẹ̀ Ẹ̀kọ́ Pípé wà lórí Ohun Èlò Green Bridge
Gba ohun èlò Green Bridge CBT sórí fóònù tàbí kọ̀mpútà rẹ fún gbogbo ilé ìkàwé IGCSE: ìwé ìdánwò àtijọ́, ìlànà ìdíwọ̀n, àwòrán èrò, káàdì ìkẹ́kọ̀ọ́ àti ẹ̀kọ́ ohùn.
Ìdánwò Ẹ̀kọ́
Oriire fun ipari ẹkọ lori Database Design. Ni bayi ti o ti ṣawari naa awọn imọran bọtini ati awọn imọran, o to akoko lati fi imọ rẹ si idanwo. Ẹka yii nfunni ni ọpọlọpọ awọn adaṣe awọn ibeere ti a ṣe lati fun oye rẹ lokun ati ṣe iranlọwọ fun ọ lati ṣe iwọn oye ohun elo naa.
Iwọ yoo pade adalu awọn iru ibeere, pẹlu awọn ibeere olumulo pupọ, awọn ibeere idahun kukuru, ati awọn ibeere iwe kikọ. Gbogbo ibeere kọọkan ni a ṣe pẹlu iṣaro lati ṣe ayẹwo awọn ẹya oriṣiriṣi ti imọ rẹ ati awọn ogbon ironu pataki.
Lo ise abala yii gege bi anfaani lati mu oye re lori koko-ọrọ naa lagbara ati lati ṣe idanimọ eyikeyi agbegbe ti o le nilo afikun ikẹkọ. Maṣe jẹ ki awọn italaya eyikeyi ti o ba pade da ọ lójú; dipo, wo wọn gẹgẹ bi awọn anfaani fun idagbasoke ati ilọsiwaju.
- Which data type is most appropriate for a field storing a telephone number? A. Integer B. Real C. String D. Boolean Answer: C
- For which of these fields is it appropriate to give a length? A. A Boolean field recording whether a fee has been paid B. A string field holding a surname C. An integer field holding a quantity D. A real field holding a price Answer: B
- In the notation used by this specification, how is the primary key of a table indicated? A. It is written in capital letters B. It is underlined C. It is placed in square brackets D. It is written last in the list Answer: B
- One member may make many bookings, and each booking is made by one member. Where should the foreign key be placed? A. In the Member table B. In the Booking table C. In both tables D. In neither table Answer: B
- What is the maximum number of tables the specification says an examined design scenario will require? A. Two B. Three C. Four D. There is no limit Answer: B
Ṣiṣẹ́ lórí àwọn ìbéèrè wọ̀nyí nínú ohun èlò náà
Ṣiṣẹ́ lórí àwọn ìbéèrè wọ̀nyí nínú ohun èlò náà
Awọn Iwe Itọsọna Ti a Gba Nimọran
Ṣe Adaṣe Awọn Ibeere Idanwo Adaṣe
Ṣe o fẹ ṣe adaṣe awọn ibeere idanwo adaṣe nipa Database Design? Ṣe igbasilẹ ohun elo Green Bridge CBT lati wọle si awọn ibeere idanwo adaṣe ati awọn ayẹwo adaṣe kikun fun koko-ọrọ yii.
Ṣe igbasilẹ ohun elo naa lori Google Playstore
Gbogbo ohun ti o nilo lati ṣe dara julọ ninu JAMB, WAEC ati NECO.
