33:I[196793,["/_next/static/chunks/1xyh1u_ku6jw-.js?dpl=nogit-1791882788","/_next/static/chunks/2_6olli-sutu3.js?dpl=nogit-1791882788","/_next/static/chunks/1qp4g--o6-1vf.js?dpl=nogit-1791882788","/_next/static/chunks/0psy-n5us57a4.js?dpl=nogit-1791882788","/_next/static/chunks/3mz725-y91ph6.js?dpl=nogit-1791882788","/_next/static/chunks/2x_dbpl3b_l2r.js?dpl=nogit-1791882788","/_next/static/chunks/0nojijad0occ8.js?dpl=nogit-1791882788","/_next/static/chunks/19ua1o9n5v3ho.js?dpl=nogit-1791882788","/_next/static/chunks/0zkcxwtbsqliz.js?dpl=nogit-1791882788","/_next/static/chunks/3yfg2hrj9oxbd.js?dpl=nogit-1791882788","/_next/static/chunks/35s1d7gs3nyqk.js?dpl=nogit-1791882788","/_next/static/chunks/38w1x0vrld4-w.js?dpl=nogit-1791882788","/_next/static/chunks/3jpl-42mbad5n.js?dpl=nogit-1791882788","/_next/static/chunks/3kzt2piec6aoa.js?dpl=nogit-1791882788","/_next/static/chunks/2lsi6eli88uwt.js?dpl=nogit-1791882788","/_next/static/chunks/2os7nxouq91eq.js?dpl=nogit-1791882788","/_next/static/chunks/3ml3vooxhiupb.js?dpl=nogit-1791882788","/_next/static/chunks/04zr-wqafvwoa.js?dpl=nogit-1791882788","/_next/static/chunks/36r9y5g_s4k64.js?dpl=nogit-1791882788","/_next/static/chunks/40lyu17d590zu.js?dpl=nogit-1791882788","/_next/static/chunks/2g-t2n9ahs3tn.js?dpl=nogit-1791882788","/_next/static/chunks/2mv9l1xl_aa4j.js?dpl=nogit-1791882788","/_next/static/chunks/44w2c3xxfw4wd.js?dpl=nogit-1791882788","/_next/static/chunks/16jtsbm2g52s0.js?dpl=nogit-1791882788","/_next/static/chunks/05mo4k9k-ry1n.js?dpl=nogit-1791882788","/_next/static/chunks/0v4byuex1x38h.js?dpl=nogit-1791882788","/_next/static/chunks/2eanemqjnv2vr.js?dpl=nogit-1791882788","/_next/static/chunks/2f3ohq_f1uov2.js?dpl=nogit-1791882788","/_next/static/chunks/0llqhg6-bxn_b.js?dpl=nogit-1791882788","/_next/static/chunks/2dx-vzwyw9a3g.js?dpl=nogit-1791882788","/_next/static/chunks/0qeo40bqomvxa.js?dpl=nogit-1791882788","/_next/static/chunks/1ku-vdy4ggo41.js?dpl=nogit-1791882788","/_next/static/chunks/1coblm1-go81_.js?dpl=nogit-1791882788","/_next/static/chunks/27ftpb6yvr6lz.js?dpl=nogit-1791882788","/_next/static/chunks/0k-y_4mcfub-p.js?dpl=nogit-1791882788","/_next/static/chunks/1o4x0l2qh0ta-.js?dpl=nogit-1791882788","/_next/static/chunks/3it1o0ex-l5qz.js?dpl=nogit-1791882788","/_next/static/chunks/2gqripb6ybmw9.js?dpl=nogit-1791882788","/_next/static/chunks/2l63yczi1z2qz.js?dpl=nogit-1791882788","/_next/static/chunks/075i0tnxt4not.js?dpl=nogit-1791882788","/_next/static/chunks/1eyu-5752jh17.js?dpl=nogit-1791882788","/_next/static/chunks/1of_-ow2iz1cj.js?dpl=nogit-1791882788","/_next/static/chunks/3ybwgs28on6c8.js?dpl=nogit-1791882788","/_next/static/chunks/13gj59kzq50t_.js?dpl=nogit-1791882788","/_next/static/chunks/1986062z5zb0v.js?dpl=nogit-1791882788","/_next/static/chunks/0uitbylhcd4am.js?dpl=nogit-1791882788","/_next/static/chunks/0wv8cpdr6cvhr.js?dpl=nogit-1791882788","/_next/static/chunks/06b61oz__qen3.js?dpl=nogit-1791882788","/_next/static/chunks/0a4x2f2g83l7b.js?dpl=nogit-1791882788","/_next/static/chunks/1lsxkfxy262n-.js?dpl=nogit-1791882788","/_next/static/chunks/3q5gc8lbwr4b4.js?dpl=nogit-1791882788","/_next/static/chunks/0dspbdeiizrn3.js?dpl=nogit-1791882788","/_next/static/chunks/2yss1g0cimuwe.js?dpl=nogit-1791882788","/_next/static/chunks/0e7v08pdxbxe2.js?dpl=nogit-1791882788","/_next/static/chunks/36nndwkz7iik3.js?dpl=nogit-1791882788","/_next/static/chunks/0zg1om_k0m5zv.js?dpl=nogit-1791882788","/_next/static/chunks/2fnth9-t6i7kd.js?dpl=nogit-1791882788","/_next/static/chunks/24srd-xd1m5z8.js?dpl=nogit-1791882788","/_next/static/chunks/0a57o9qvnv-nb.js?dpl=nogit-1791882788","/_next/static/chunks/41hx021qkamew.js?dpl=nogit-1791882788","/_next/static/chunks/1ksyn9m68446d.js?dpl=nogit-1791882788"],"Gingerbread"] 35:I[647935,["/_next/static/chunks/1xyh1u_ku6jw-.js?dpl=nogit-1791882788","/_next/static/chunks/2_6olli-sutu3.js?dpl=nogit-1791882788","/_next/static/chunks/1qp4g--o6-1vf.js?dpl=nogit-1791882788","/_next/static/chunks/0psy-n5us57a4.js?dpl=nogit-1791882788","/_next/static/chunks/3mz725-y91ph6.js?dpl=nogit-1791882788","/_next/static/chunks/2x_dbpl3b_l2r.js?dpl=nogit-1791882788","/_next/static/chunks/0nojijad0occ8.js?dpl=nogit-1791882788","/_next/static/chunks/19ua1o9n5v3ho.js?dpl=nogit-1791882788","/_next/static/chunks/0zkcxwtbsqliz.js?dpl=nogit-1791882788","/_next/static/chunks/3yfg2hrj9oxbd.js?dpl=nogit-1791882788","/_next/static/chunks/35s1d7gs3nyqk.js?dpl=nogit-1791882788","/_next/static/chunks/38w1x0vrld4-w.js?dpl=nogit-1791882788","/_next/static/chunks/3jpl-42mbad5n.js?dpl=nogit-1791882788","/_next/static/chunks/3kzt2piec6aoa.js?dpl=nogit-1791882788","/_next/static/chunks/2lsi6eli88uwt.js?dpl=nogit-1791882788","/_next/static/chunks/2os7nxouq91eq.js?dpl=nogit-1791882788","/_next/static/chunks/3ml3vooxhiupb.js?dpl=nogit-1791882788","/_next/static/chunks/04zr-wqafvwoa.js?dpl=nogit-1791882788","/_next/static/chunks/36r9y5g_s4k64.js?dpl=nogit-1791882788","/_next/static/chunks/40lyu17d590zu.js?dpl=nogit-1791882788","/_next/static/chunks/2g-t2n9ahs3tn.js?dpl=nogit-1791882788","/_next/static/chunks/2mv9l1xl_aa4j.js?dpl=nogit-1791882788","/_next/static/chunks/44w2c3xxfw4wd.js?dpl=nogit-1791882788","/_next/static/chunks/16jtsbm2g52s0.js?dpl=nogit-1791882788","/_next/static/chunks/05mo4k9k-ry1n.js?dpl=nogit-1791882788","/_next/static/chunks/0v4byuex1x38h.js?dpl=nogit-1791882788","/_next/static/chunks/2eanemqjnv2vr.js?dpl=nogit-1791882788","/_next/static/chunks/2f3ohq_f1uov2.js?dpl=nogit-1791882788","/_next/static/chunks/0llqhg6-bxn_b.js?dpl=nogit-1791882788","/_next/static/chunks/2dx-vzwyw9a3g.js?dpl=nogit-1791882788","/_next/static/chunks/0qeo40bqomvxa.js?dpl=nogit-1791882788","/_next/static/chunks/1ku-vdy4ggo41.js?dpl=nogit-1791882788","/_next/static/chunks/1coblm1-go81_.js?dpl=nogit-1791882788","/_next/static/chunks/27ftpb6yvr6lz.js?dpl=nogit-1791882788","/_next/static/chunks/0k-y_4mcfub-p.js?dpl=nogit-1791882788","/_next/static/chunks/1o4x0l2qh0ta-.js?dpl=nogit-1791882788","/_next/static/chunks/3it1o0ex-l5qz.js?dpl=nogit-1791882788","/_next/static/chunks/2gqripb6ybmw9.js?dpl=nogit-1791882788","/_next/static/chunks/2l63yczi1z2qz.js?dpl=nogit-1791882788","/_next/static/chunks/075i0tnxt4not.js?dpl=nogit-1791882788","/_next/static/chunks/1eyu-5752jh17.js?dpl=nogit-1791882788","/_next/static/chunks/1of_-ow2iz1cj.js?dpl=nogit-1791882788","/_next/static/chunks/3ybwgs28on6c8.js?dpl=nogit-1791882788","/_next/static/chunks/13gj59kzq50t_.js?dpl=nogit-1791882788","/_next/static/chunks/1986062z5zb0v.js?dpl=nogit-1791882788","/_next/static/chunks/0uitbylhcd4am.js?dpl=nogit-1791882788","/_next/static/chunks/0wv8cpdr6cvhr.js?dpl=nogit-1791882788","/_next/static/chunks/06b61oz__qen3.js?dpl=nogit-1791882788","/_next/static/chunks/0a4x2f2g83l7b.js?dpl=nogit-1791882788","/_next/static/chunks/1lsxkfxy262n-.js?dpl=nogit-1791882788","/_next/static/chunks/3q5gc8lbwr4b4.js?dpl=nogit-1791882788","/_next/static/chunks/0dspbdeiizrn3.js?dpl=nogit-1791882788","/_next/static/chunks/2yss1g0cimuwe.js?dpl=nogit-1791882788","/_next/static/chunks/0e7v08pdxbxe2.js?dpl=nogit-1791882788","/_next/static/chunks/36nndwkz7iik3.js?dpl=nogit-1791882788","/_next/static/chunks/0zg1om_k0m5zv.js?dpl=nogit-1791882788","/_next/static/chunks/2fnth9-t6i7kd.js?dpl=nogit-1791882788","/_next/static/chunks/24srd-xd1m5z8.js?dpl=nogit-1791882788","/_next/static/chunks/0a57o9qvnv-nb.js?dpl=nogit-1791882788","/_next/static/chunks/41hx021qkamew.js?dpl=nogit-1791882788","/_next/static/chunks/1ksyn9m68446d.js?dpl=nogit-1791882788"],"RecordResourceResume"] 36:I[830476,["/_next/static/chunks/1xyh1u_ku6jw-.js?dpl=nogit-1791882788","/_next/static/chunks/2_6olli-sutu3.js?dpl=nogit-1791882788","/_next/static/chunks/1qp4g--o6-1vf.js?dpl=nogit-1791882788","/_next/static/chunks/0psy-n5us57a4.js?dpl=nogit-1791882788","/_next/static/chunks/3mz725-y91ph6.js?dpl=nogit-1791882788","/_next/static/chunks/2x_dbpl3b_l2r.js?dpl=nogit-1791882788","/_next/static/chunks/0nojijad0occ8.js?dpl=nogit-1791882788","/_next/static/chunks/19ua1o9n5v3ho.js?dpl=nogit-1791882788","/_next/static/chunks/0zkcxwtbsqliz.js?dpl=nogit-1791882788","/_next/static/chunks/3yfg2hrj9oxbd.js?dpl=nogit-1791882788","/_next/static/chunks/35s1d7gs3nyqk.js?dpl=nogit-1791882788","/_next/static/chunks/38w1x0vrld4-w.js?dpl=nogit-1791882788","/_next/static/chunks/3jpl-42mbad5n.js?dpl=nogit-1791882788","/_next/static/chunks/3kzt2piec6aoa.js?dpl=nogit-1791882788","/_next/static/chunks/2lsi6eli88uwt.js?dpl=nogit-1791882788","/_next/static/chunks/2os7nxouq91eq.js?dpl=nogit-1791882788","/_next/static/chunks/3ml3vooxhiupb.js?dpl=nogit-1791882788","/_next/static/chunks/04zr-wqafvwoa.js?dpl=nogit-1791882788","/_next/static/chunks/36r9y5g_s4k64.js?dpl=nogit-1791882788","/_next/static/chunks/40lyu17d590zu.js?dpl=nogit-1791882788","/_next/static/chunks/2g-t2n9ahs3tn.js?dpl=nogit-1791882788","/_next/static/chunks/2mv9l1xl_aa4j.js?dpl=nogit-1791882788","/_next/static/chunks/44w2c3xxfw4wd.js?dpl=nogit-1791882788","/_next/static/chunks/16jtsbm2g52s0.js?dpl=nogit-1791882788","/_next/static/chunks/05mo4k9k-ry1n.js?dpl=nogit-1791882788","/_next/static/chunks/0v4byuex1x38h.js?dpl=nogit-1791882788","/_next/static/chunks/2eanemqjnv2vr.js?dpl=nogit-1791882788","/_next/static/chunks/2f3ohq_f1uov2.js?dpl=nogit-1791882788","/_next/static/chunks/0llqhg6-bxn_b.js?dpl=nogit-1791882788","/_next/static/chunks/2dx-vzwyw9a3g.js?dpl=nogit-1791882788","/_next/static/chunks/0qeo40bqomvxa.js?dpl=nogit-1791882788","/_next/static/chunks/1ku-vdy4ggo41.js?dpl=nogit-1791882788","/_next/static/chunks/1coblm1-go81_.js?dpl=nogit-1791882788","/_next/static/chunks/27ftpb6yvr6lz.js?dpl=nogit-1791882788","/_next/static/chunks/0k-y_4mcfub-p.js?dpl=nogit-1791882788","/_next/static/chunks/1o4x0l2qh0ta-.js?dpl=nogit-1791882788","/_next/static/chunks/3it1o0ex-l5qz.js?dpl=nogit-1791882788","/_next/static/chunks/2gqripb6ybmw9.js?dpl=nogit-1791882788","/_next/static/chunks/2l63yczi1z2qz.js?dpl=nogit-1791882788","/_next/static/chunks/075i0tnxt4not.js?dpl=nogit-1791882788","/_next/static/chunks/1eyu-5752jh17.js?dpl=nogit-1791882788","/_next/static/chunks/1of_-ow2iz1cj.js?dpl=nogit-1791882788","/_next/static/chunks/3ybwgs28on6c8.js?dpl=nogit-1791882788","/_next/static/chunks/13gj59kzq50t_.js?dpl=nogit-1791882788","/_next/static/chunks/1986062z5zb0v.js?dpl=nogit-1791882788","/_next/static/chunks/0uitbylhcd4am.js?dpl=nogit-1791882788","/_next/static/chunks/0wv8cpdr6cvhr.js?dpl=nogit-1791882788","/_next/static/chunks/06b61oz__qen3.js?dpl=nogit-1791882788","/_next/static/chunks/0a4x2f2g83l7b.js?dpl=nogit-1791882788","/_next/static/chunks/1lsxkfxy262n-.js?dpl=nogit-1791882788","/_next/static/chunks/3q5gc8lbwr4b4.js?dpl=nogit-1791882788","/_next/static/chunks/0dspbdeiizrn3.js?dpl=nogit-1791882788","/_next/static/chunks/2yss1g0cimuwe.js?dpl=nogit-1791882788","/_next/static/chunks/0e7v08pdxbxe2.js?dpl=nogit-1791882788","/_next/static/chunks/36nndwkz7iik3.js?dpl=nogit-1791882788","/_next/static/chunks/0zg1om_k0m5zv.js?dpl=nogit-1791882788","/_next/static/chunks/2fnth9-t6i7kd.js?dpl=nogit-1791882788","/_next/static/chunks/24srd-xd1m5z8.js?dpl=nogit-1791882788","/_next/static/chunks/0a57o9qvnv-nb.js?dpl=nogit-1791882788","/_next/static/chunks/41hx021qkamew.js?dpl=nogit-1791882788","/_next/static/chunks/1ksyn9m68446d.js?dpl=nogit-1791882788"],"FlashcardAccessBranch"] 37:I[315438,["/_next/static/chunks/1xyh1u_ku6jw-.js?dpl=nogit-1791882788","/_next/static/chunks/2_6olli-sutu3.js?dpl=nogit-1791882788","/_next/static/chunks/1qp4g--o6-1vf.js?dpl=nogit-1791882788","/_next/static/chunks/0psy-n5us57a4.js?dpl=nogit-1791882788","/_next/static/chunks/3mz725-y91ph6.js?dpl=nogit-1791882788","/_next/static/chunks/2x_dbpl3b_l2r.js?dpl=nogit-1791882788","/_next/static/chunks/0nojijad0occ8.js?dpl=nogit-1791882788","/_next/static/chunks/19ua1o9n5v3ho.js?dpl=nogit-1791882788","/_next/static/chunks/0zkcxwtbsqliz.js?dpl=nogit-1791882788","/_next/static/chunks/3yfg2hrj9oxbd.js?dpl=nogit-1791882788","/_next/static/chunks/35s1d7gs3nyqk.js?dpl=nogit-1791882788","/_next/static/chunks/38w1x0vrld4-w.js?dpl=nogit-1791882788","/_next/static/chunks/3jpl-42mbad5n.js?dpl=nogit-1791882788","/_next/static/chunks/3kzt2piec6aoa.js?dpl=nogit-1791882788","/_next/static/chunks/2lsi6eli88uwt.js?dpl=nogit-1791882788","/_next/static/chunks/2os7nxouq91eq.js?dpl=nogit-1791882788","/_next/static/chunks/3ml3vooxhiupb.js?dpl=nogit-1791882788","/_next/static/chunks/04zr-wqafvwoa.js?dpl=nogit-1791882788","/_next/static/chunks/36r9y5g_s4k64.js?dpl=nogit-1791882788","/_next/static/chunks/40lyu17d590zu.js?dpl=nogit-1791882788","/_next/static/chunks/2g-t2n9ahs3tn.js?dpl=nogit-1791882788","/_next/static/chunks/2mv9l1xl_aa4j.js?dpl=nogit-1791882788","/_next/static/chunks/44w2c3xxfw4wd.js?dpl=nogit-1791882788","/_next/static/chunks/16jtsbm2g52s0.js?dpl=nogit-1791882788","/_next/static/chunks/05mo4k9k-ry1n.js?dpl=nogit-1791882788","/_next/static/chunks/0v4byuex1x38h.js?dpl=nogit-1791882788","/_next/static/chunks/2eanemqjnv2vr.js?dpl=nogit-1791882788","/_next/static/chunks/2f3ohq_f1uov2.js?dpl=nogit-1791882788","/_next/static/chunks/0llqhg6-bxn_b.js?dpl=nogit-1791882788","/_next/static/chunks/2dx-vzwyw9a3g.js?dpl=nogit-1791882788","/_next/static/chunks/0qeo40bqomvxa.js?dpl=nogit-1791882788","/_next/static/chunks/1ku-vdy4ggo41.js?dpl=nogit-1791882788","/_next/static/chunks/1coblm1-go81_.js?dpl=nogit-1791882788","/_next/static/chunks/27ftpb6yvr6lz.js?dpl=nogit-1791882788","/_next/static/chunks/0k-y_4mcfub-p.js?dpl=nogit-1791882788","/_next/static/chunks/1o4x0l2qh0ta-.js?dpl=nogit-1791882788","/_next/static/chunks/3it1o0ex-l5qz.js?dpl=nogit-1791882788","/_next/static/chunks/2gqripb6ybmw9.js?dpl=nogit-1791882788","/_next/static/chunks/2l63yczi1z2qz.js?dpl=nogit-1791882788","/_next/static/chunks/075i0tnxt4not.js?dpl=nogit-1791882788","/_next/static/chunks/1eyu-5752jh17.js?dpl=nogit-1791882788","/_next/static/chunks/1of_-ow2iz1cj.js?dpl=nogit-1791882788","/_next/static/chunks/3ybwgs28on6c8.js?dpl=nogit-1791882788","/_next/static/chunks/13gj59kzq50t_.js?dpl=nogit-1791882788","/_next/static/chunks/1986062z5zb0v.js?dpl=nogit-1791882788","/_next/static/chunks/0uitbylhcd4am.js?dpl=nogit-1791882788","/_next/static/chunks/0wv8cpdr6cvhr.js?dpl=nogit-1791882788","/_next/static/chunks/06b61oz__qen3.js?dpl=nogit-1791882788","/_next/static/chunks/0a4x2f2g83l7b.js?dpl=nogit-1791882788","/_next/static/chunks/1lsxkfxy262n-.js?dpl=nogit-1791882788","/_next/static/chunks/3q5gc8lbwr4b4.js?dpl=nogit-1791882788","/_next/static/chunks/0dspbdeiizrn3.js?dpl=nogit-1791882788","/_next/static/chunks/2yss1g0cimuwe.js?dpl=nogit-1791882788","/_next/static/chunks/0e7v08pdxbxe2.js?dpl=nogit-1791882788","/_next/static/chunks/36nndwkz7iik3.js?dpl=nogit-1791882788","/_next/static/chunks/0zg1om_k0m5zv.js?dpl=nogit-1791882788","/_next/static/chunks/2fnth9-t6i7kd.js?dpl=nogit-1791882788","/_next/static/chunks/24srd-xd1m5z8.js?dpl=nogit-1791882788","/_next/static/chunks/0a57o9qvnv-nb.js?dpl=nogit-1791882788","/_next/static/chunks/41hx021qkamew.js?dpl=nogit-1791882788","/_next/static/chunks/1ksyn9m68446d.js?dpl=nogit-1791882788"],"TopicFlashcardRunner"] 24:[["$","$L33",null,{"feature":"flashcards"}],"$L34",["$","$L35",null,{"href":"/a-level/computer-science/aqa/relational-databases/flashcards","label":"Relational databases","subjectCode":"a_level_computer_science__aqa","surface":"flashcards"}],["$","$L36",null,{"runner":["$","div",null,{"className":"min-h-0 flex-1 overflow-hidden bg-background","children":["$","$L37",null,{"decks":[{"id":"c6309223-ad07-4800-a2d1-90aec4119ba2","title":"Relational databases Flashcards","topicId":"6f2bd44f-0565-5198-a6ef-ba22570e6a4f","topicSlug":"relational-databases","cards":[{"id":"53533fee-51aa-49a3-9ffd-337d52bd3cea","cardType":"basic","points":1,"front":"In a relational database, what is a table called?","back":"A relation.","mcqOptions":[{"text":"A relation.","correct":true,"explanation":"In the relational model, a table is formally called a relation because it represents a set of related records with the same defined attributes."},{"text":"A record.","correct":false,"explanation":"A record is one row within a table, not the table itself. In relational database terminology, the entire table is called a relation."},{"text":"A field.","correct":false,"explanation":"A field stores an individual data value within a record, so it is not a whole table. A relational database table is called a relation."},{"text":"A query.","correct":false,"explanation":"A query is an instruction used to retrieve or manipulate database data, not a name for its storage structure. A table is formally called a relation."}]},{"id":"a0a1bd48-abdc-40b7-98f6-d3819209958a","cardType":"basic","points":1,"front":"In a table, what does one row represent?","back":"One record - one instance of the entity.","mcqOptions":[{"text":"One record - one instance of the entity.","correct":true,"explanation":"Each row contains all the stored attribute values for one entity instance, so a row represents a single record in the table."},{"text":"One attribute - one property of the entity.","correct":false,"explanation":"An attribute is represented by a named column, not by a row. A row is one record containing data about one instance of the entity."},{"text":"One field - one value belonging to the entity.","correct":false,"explanation":"A field is an individual value at the intersection of a row and column. The complete row represents one record, or one entity instance."},{"text":"One relation - one collection of the entity.","correct":false,"explanation":"A relation is the whole table rather than an individual row. Each row within that relation is one record representing one instance of the entity."}]},{"id":"976e3e5c-5f3b-4efc-81f3-e997f510580e","cardType":"basic","points":1,"front":"In a table, what does a named column store?","back":"An attribute - one piece of data about each record.","mcqOptions":[{"text":"An attribute - one piece of data about each record.","correct":true,"explanation":"A named column represents an attribute, defining one particular property that is stored for every applicable record in the table."},{"text":"A record - one complete instance stored in the table.","correct":false,"explanation":"A record is an entire row containing several attribute values. A named column instead stores one attribute, or one type of data, about each record."},{"text":"A relation - one complete set of related records.","correct":false,"explanation":"A relation is the complete table, not one named column. Each named column defines an attribute that stores one piece of data about every record."},{"text":"A foreign key - one link to every other table.","correct":false,"explanation":"Only certain columns are foreign keys used to reference another table. A named column generally represents an attribute, whether or not it is a key."}]},{"id":"8be7252f-ad05-49a3-8354-7afa52201451","cardType":"cloze","points":null,"front":"A relational database stores data in related tables called [ ].","back":"A relational database stores data in related tables called relations.","mcqOptions":[{"text":"relations","correct":true,"explanation":"The relational model organises data into tables formally known as relations, with each relation consisting of records arranged using a defined set of attributes."},{"text":"records","correct":false,"explanation":"Records are the individual rows held within tables, not the tables themselves. In formal relational database terminology, the tables are called relations."},{"text":"attributes","correct":false,"explanation":"Attributes are the named columns that describe properties of records. The related tables containing those attributes and records are formally called relations."},{"text":"fields","correct":false,"explanation":"Fields are individual data items or positions within records, not complete tables. Tables in a relational database are formally known as relations."}]},{"id":"6630ac1a-95bf-492a-bbd5-fdf5204b94f3","cardType":"basic","points":1,"front":"What does each table in a relational database normally store data about?","back":"One type of entity.","mcqOptions":[{"text":"One type of entity.","correct":true,"explanation":"A table normally models one entity type, such as STUDENT or COURSE, while each row represents one particular instance of that entity."},{"text":"One type of attribute.","correct":false,"explanation":"An attribute is a property represented by a column, such as CourseName. A whole table normally stores records belonging to one type of entity."},{"text":"One instance of an entity.","correct":false,"explanation":"One entity instance is represented by a single row, not the whole table. The table normally contains many instances of one entity type."},{"text":"One complete database.","correct":false,"explanation":"A database usually contains several related tables rather than being represented by one table. Each table normally stores data about one type of entity."}]},{"id":"14cb2e81-f6ef-4495-a3af-619468eade07","cardType":"basic","points":1,"front":"How are rows in different relational database tables usually linked?","back":"By shared key values.","mcqOptions":[{"text":"By shared key values.","correct":true,"explanation":"A primary key value in one table can appear as a foreign key in another, allowing corresponding records in the two tables to be linked."},{"text":"By matching row positions.","correct":false,"explanation":"Row order and position are not reliable identifiers and can change when data is sorted. Tables are linked using matching primary and foreign key values."},{"text":"By identical table names.","correct":false,"explanation":"Table names identify whole relations and are normally different, so they do not connect individual records. Links are created using shared key values."},{"text":"By common column widths.","correct":false,"explanation":"Column display width has no role in database relationships and may vary between interfaces. Records in different tables are linked through shared key values."}]},{"id":"1a8810be-c58e-435d-8ae9-93bf903a088c","cardType":"cloze","points":null,"front":"A relational database usually links tables using shared identifiers, not by storing one table [ ] another.","back":"A relational database usually links tables using shared identifiers, not by storing one table physically inside another.","mcqOptions":[{"text":"physically inside","correct":true,"explanation":"Relational tables remain separate structures and are connected logically through matching identifiers, such as primary and foreign keys, rather than being physically nested inside one another."},{"text":"directly underneath","correct":false,"explanation":"The visual or physical position of tables does not establish a relationship. Separate tables are linked logically through shared primary and foreign key values."},{"text":"alphabetically before","correct":false,"explanation":"Alphabetical ordering of table names has no effect on relationships between their records. Relational databases create links by matching shared key values."},{"text":"as a row within","correct":false,"explanation":"A row represents one record of a table and cannot contain another complete table in the relational model. Separate tables are linked using shared identifiers."}]},{"id":"e45fa2ab-36d6-48d4-b2ea-36306d3ee77e","cardType":"basic","points":1,"front":"Why split course details into a separate COURSE table?","back":"To reduce duplicated course data.","mcqOptions":[{"text":"To reduce duplicated course data.","correct":true,"explanation":"Storing each course once in a COURSE table prevents details such as its title from being repeated for every student enrolled on that course."},{"text":"To reduce duplicated student data.","correct":false,"explanation":"Separating course details specifically removes repeated information about courses, not repeated student details. Student data would be normalised separately in a STUDENT table."},{"text":"To reduce the number of tables.","correct":false,"explanation":"Creating a separate COURSE table increases the number of tables rather than reducing it. Its purpose is to reduce duplicated course data through normalisation."},{"text":"To avoid using foreign keys.","correct":false,"explanation":"Splitting course data normally requires a foreign key to link records to the COURSE table. The separation is performed to reduce duplicated course data."}]},{"id":"ccc24f64-4723-40d5-a1b7-9b78f650479e","cardType":"basic","points":1,"front":"If a teacher changes, why is storing course details once better?","back":"Only one COURSE row needs updating.","mcqOptions":[{"text":"Only one COURSE row needs updating.","correct":true,"explanation":"Storing each course once removes duplicated course details. If its teacher changes, updating the single COURSE record keeps every use of that course information consistent."},{"text":"Every STUDENT row needs updating.","correct":false,"explanation":"Updating every STUDENT row would be necessary only if course information were duplicated there. With normalised data, the right answer is that only one COURSE row needs updating."},{"text":"Every ENROLMENT row needs updating.","correct":false,"explanation":"This assumes the teacher’s details are repeated in each enrolment record, creating an update anomaly. Storing them once means only one COURSE row needs updating."},{"text":"Only one STUDENT row needs updating.","correct":false,"explanation":"A change of teacher concerns the course, not one particular student. The course information is stored centrally, so only one COURSE row needs updating."}]},{"id":"ddd50c63-3ad8-4b9c-942b-ff63d7113143","cardType":"basic","points":1,"front":"What problem can occur if repeated data is updated in some rows but not others?","back":"The data becomes inconsistent.","mcqOptions":[{"text":"The data becomes inconsistent.","correct":true,"explanation":"Updating only some copies leaves different values for the same fact in different rows. The database then contains contradictory, inconsistent data."},{"text":"The data becomes encrypted.","correct":false,"explanation":"Encryption deliberately encodes data for security and is unrelated to partial updates. Updating some repeated values but not others makes the data inconsistent."},{"text":"The data becomes validated.","correct":false,"explanation":"Validation checks whether input follows specified rules; it does not resolve conflicting copies. Partial updates to repeated data cause the database to become inconsistent."},{"text":"The data becomes normalised.","correct":false,"explanation":"Normalisation reduces repeated data and helps prevent this problem; it is not caused by partial updates. The conflicting values make the data inconsistent."}]},{"id":"55b10644-b85b-4129-b8df-856ee1e526a0","cardType":"cloze","points":null,"front":"A primary key must [ ] each record in its table.","back":"A primary key must uniquely identify each record in its table.","mcqOptions":[{"text":"uniquely identify","correct":true,"explanation":"A primary key distinguishes every record from all others, so its value must uniquely identify one record within the table."},{"text":"alphabetically order","correct":false,"explanation":"A primary key may be used for indexing, but it does not have to arrange records alphabetically. Its essential role is to uniquely identify each record."},{"text":"automatically validate","correct":false,"explanation":"Validation checks whether entered data meets rules, whereas a primary key identifies records. The blank must be “uniquely identify” because no two records may share its value."},{"text":"numerically calculate","correct":false,"explanation":"Primary keys can contain numbers, but their purpose is not to perform calculations. They must uniquely identify each record regardless of the key’s data type."}]},{"id":"5e4904f8-874c-4e02-bbf1-7102cb4a6aee","cardType":"basic","points":2,"front":"Why is Name usually a poor primary key in a STUDENT table?","back":"Names may repeat or change.","mcqOptions":[{"text":"Names may repeat or change.","correct":true,"explanation":"Different students can have the same name, and a student’s name can change. A primary key must remain unique and stable, so Name is unsuitable."},{"text":"Names may validate or calculate.","correct":false,"explanation":"Validation and calculation are operations, not weaknesses of names as keys. Name is usually unsuitable because names may repeat between students or change over time."},{"text":"Names may encrypt or compress.","correct":false,"explanation":"Encryption and compression do not determine whether an attribute is a suitable primary key. Names are poor keys because they may repeat or change."},{"text":"Names may sort or filter.","correct":false,"explanation":"Being sortable or filterable does not prevent an attribute from being a primary key. The problem is that names may repeat or change, violating uniqueness or stability."}]},{"id":"911ad6c4-f14a-48b6-8900-42924458225a","cardType":"basic","points":2,"front":"What must be true about primary key values in a table?","back":"They must be unique and present.","mcqOptions":[{"text":"They must be unique and present.","correct":true,"explanation":"Every primary key value must distinguish its record from all others and cannot be missing. Therefore, key values must be unique and present."},{"text":"They must be repeated and optional.","correct":false,"explanation":"Repeated values would identify multiple records, while optional values could be null. Primary key values must instead be unique and present in every record."},{"text":"They must be alphabetical and sorted.","correct":false,"explanation":"Primary keys do not need to contain letters or appear in sorted order. Their required properties are that every value is unique and present."},{"text":"They must be numeric and calculated.","correct":false,"explanation":"A primary key can use non-numeric data and need not be derived by calculation. What matters is that its values are unique and always present."}]},{"id":"bd014559-7440-42aa-b795-088f95925645","cardType":"cloze","points":null,"front":"A good primary key should be unique, present and [ ].","back":"A good primary key should be unique, present and stable.","mcqOptions":[{"text":"stable","correct":true,"explanation":"A stable key rarely or never changes, so relationships referencing it remain valid. Alongside being unique and present, this makes it suitable for identifying records."},{"text":"repeated","correct":false,"explanation":"A repeated value would identify more than one record and directly violate the uniqueness requirement. A good primary key should instead be stable over time."},{"text":"optional","correct":false,"explanation":"An optional key could be absent, contradicting the requirement that every primary key value is present. The intended additional property is that the key is stable."},{"text":"editable","correct":false,"explanation":"Frequently editable values are poor keys because changes can disrupt references from related tables. A good primary key should be stable rather than expected to change."}]},{"id":"24f3c773-6f37-4a0a-9f82-4e66917dac2d","cardType":"basic","points":2,"front":"In the example STUDENT table, why is StudentID the best primary key?","back":"Each StudentID is different and controlled by the school.","mcqOptions":[{"text":"Each StudentID is different and controlled by the school.","correct":true,"explanation":"The school can ensure that every StudentID is unique, present and stable. This makes it a reliable identifier for each student record."},{"text":"Each StudentID is repeated and chosen by the student.","correct":false,"explanation":"Repeated identifiers could refer to several students, and student-chosen values may not be reliably controlled. StudentID is best because each is different and school-controlled."},{"text":"Each StudentID is identical and changed by the school.","correct":false,"explanation":"Identical values could not distinguish individual records, while changing identifiers would make them unstable. The correct reason is that each StudentID is different and school-controlled."},{"text":"Each StudentID is optional and based on the student’s name.","correct":false,"explanation":"A primary key cannot be optional, and names may repeat or change. StudentID is suitable because every value is different and controlled by the school."}]},{"id":"9a327137-34e0-4d3b-b0bc-601a76cbfd65","cardType":"basic","points":1,"front":"When is a composite primary key needed?","back":"When one attribute alone cannot uniquely identify a row.","mcqOptions":[{"text":"When one attribute alone cannot uniquely identify a row.","correct":true,"explanation":"A composite primary key combines two or more attributes when no single attribute distinguishes every record, but their combined values uniquely identify each row."},{"text":"When one attribute alone cannot alphabetically order a row.","correct":false,"explanation":"The need for alphabetical ordering does not determine key design. A composite primary key is required when one attribute alone cannot uniquely identify a row."},{"text":"When one attribute alone cannot automatically validate a row.","correct":false,"explanation":"Validation checks data against rules and is separate from record identification. Composite keys are used when one attribute alone cannot uniquely identify a row."},{"text":"When one attribute alone cannot numerically calculate a row.","correct":false,"explanation":"Primary keys identify records rather than calculate row values. A composite key is needed when no single attribute can uniquely identify the row."}]},{"id":"43a98b90-7b4a-4484-9d6c-87db0d1a59a1","cardType":"cloze","points":null,"front":"In a composite primary key, the [ ] of values must be unique, even if individual attributes repeat.","back":"In a composite primary key, the combination of values must be unique, even if individual attributes repeat.","mcqOptions":[{"text":"combination","correct":true,"explanation":"A composite primary key identifies each record through the combined values of two or more attributes, so the complete combination must be unique."},{"text":"sequence","correct":false,"explanation":"Attribute order does not make records unique. The correct term is combination because the values considered together distinguish each record."},{"text":"quantity","correct":false,"explanation":"The number of values is not what uniquely identifies a record. Their combination must be unique, even though individual values may repeat."},{"text":"range","correct":false,"explanation":"A range describes the spread of possible values, not how records are identified. The unique combination of attribute values forms the composite primary key."}]},{"id":"b010212a-b072-4bed-a64d-f0af237d8d3a","cardType":"basic","points":1,"front":"In ENROLMENT, why can StudentID and CourseID together identify one enrolment?","back":"Each student-course pair appears once.","mcqOptions":[{"text":"Each student-course pair appears once.","correct":true,"explanation":"The two identifiers together represent one particular student taking one particular course. Ensuring each pair appears once makes the pair suitable as a composite primary key."},{"text":"Each student appears once.","correct":false,"explanation":"A student may appear in several enrolment records because they can take multiple courses. It is each student-course pair that must appear once."},{"text":"Each course appears once.","correct":false,"explanation":"A course may appear in many enrolment records because many students can take it. The unique item is the student-course pair, not the course alone."},{"text":"Each student-course pair appears many times.","correct":false,"explanation":"Repeating the same pair would create duplicate enrolments and prevent it from identifying one record. Each student-course pair must appear only once."}]},{"id":"820aba9a-9e0c-4a3f-b821-f1110c79fb55","cardType":"basic","points":1,"front":"What role does ENROLMENT.StudentID have if it refers to STUDENT.StudentID?","back":"It is a foreign key.","mcqOptions":[{"text":"It is a foreign key.","correct":true,"explanation":"ENROLMENT.StudentID references the primary key of the STUDENT table, so it is a foreign key that links each enrolment to an existing student."},{"text":"It is a primary key.","correct":false,"explanation":"StudentID can repeat in ENROLMENT because one student may take several courses, so it cannot identify enrolments alone. It acts as a foreign key."},{"text":"It is a candidate key.","correct":false,"explanation":"A candidate key must uniquely identify each record, but StudentID can repeat across a student’s enrolments. Its role here is a foreign key."},{"text":"It is a secondary key.","correct":false,"explanation":"A secondary key is used mainly for searching and need not establish a table relationship. StudentID is specifically a foreign key because it references STUDENT.StudentID."}]},{"id":"12675275-1805-483b-af7e-cd5091338248","cardType":"cloze","points":null,"front":"Referential integrity means foreign key links point to [ ].","back":"Referential integrity means foreign key links point to existing records.","mcqOptions":[{"text":"existing records","correct":true,"explanation":"Referential integrity requires every non-null foreign key value to match an existing referenced record, preventing links that point to missing data."},{"text":"deleted records","correct":false,"explanation":"Allowing links to deleted records would create orphaned records and violate referential integrity. Foreign keys must point to existing records."},{"text":"unrelated records","correct":false,"explanation":"A foreign key must match a record in its designated referenced table, not an unrelated record. Referential integrity therefore requires links to existing matching records."},{"text":"new records","correct":false,"explanation":"A record being new does not guarantee that it matches the foreign key. The required condition is that the referenced record already exists."}]},{"id":"9eb4b3a0-3b2e-47f7-9c24-cdf0bd4554ac","cardType":"basic","points":1,"front":"Why can a foreign key value repeat in ENROLMENT?","back":"Many enrolments can reference the same student or course.","mcqOptions":[{"text":"Many enrolments can reference the same student or course.","correct":true,"explanation":"A student can enrol on several courses, and a course can include several students. Therefore their identifiers may legitimately occur in multiple ENROLMENT records."},{"text":"Only one enrolment can reference each student or course.","correct":false,"explanation":"This incorrectly treats foreign keys as unique values and would prevent multiple enrolments. Many enrolments can reference the same student or course."},{"text":"Every enrolment must reference a different student or course.","correct":false,"explanation":"Foreign key values do not have to be different in every record. Repetition is necessary when several enrolments involve the same student or course."},{"text":"Each enrolment can reference several students or courses.","correct":false,"explanation":"An individual foreign key field stores one reference, not a list of references. Repetition occurs because many records can reference the same student or course."}]},{"id":"523c5243-6044-47d3-8664-a0e284e7abba","cardType":"basic","points":1,"front":"How is a many-to-many relationship between students and courses represented?","back":"Using an extra ENROLMENT table.","mcqOptions":[{"text":"Using an extra ENROLMENT table.","correct":true,"explanation":"ENROLMENT acts as a junction table, storing student-course pairs through foreign keys. Each row represents one student’s participation in one course."},{"text":"Using an extra STUDENT table.","correct":false,"explanation":"Another STUDENT table would duplicate the existing entity and would not resolve the many-to-many relationship. A separate ENROLMENT junction table is required."},{"text":"Using an extra COURSE table.","correct":false,"explanation":"Another COURSE table would duplicate course data rather than connect students and courses. The relationship is represented with an ENROLMENT junction table."},{"text":"Using a list inside the STUDENT table.","correct":false,"explanation":"Storing a list of courses in one field violates first normal form because values should be atomic. An ENROLMENT table stores each student-course pair separately."}]}]}],"examCountdown":{"examDate":"2027-06-07","paperLabel":"Paper 1"},"heading":"Relational databases","title":"Relational databases Flashcards","topbar":{"backHref":"/a-level/computer-science/aqa/flashcards"},"topicSidebar":"$L38"}]}],"topicId":"6f2bd44f-0565-5198-a6ef-ba22570e6a4f","walled":"$L39"}],"$L3a","$L3b"]