Data relations(1.3.2 1) Flashcards

1
Q

What are relational databases?

A

usually created of 2D data structures called tables

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are table identifiers?

A

each table in the database needs a name

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is a record?

A

each row in a table

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is a field?

A

each column a table

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is a data element/data item?

A

each individual cell in a table

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Table and field identifier

A

case sensitive
should contain no spaces

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Tables and keys

A

the most important aspect of a table (even in a flat file) is that each record must be unique;y identifiable in some way
to do this we define a primary key

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is a primary key?

A

a field or collection of fields which uniquely identify each record

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

ID fields

A

an easy way to create a uniquely identifiable record is to simply have a field which contains an automatically generated ( often serialised) ID number
it increase the size of the database
it introduces an abstrxct piece of data which may have no relevence to real life uses

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is a foreign key?

A

a field of one table which references the primary key of a different table

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Foreign keys

A

using one produces a relation between the two tables
tables can be related to multiple other tables by use of foreign key
cannot be used as the primary key in a related table and should not be used as part of a multi field primary key

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Entities and relations

A

we can describe the relation between the tables by considering the actual relation between the objects described in the table

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

One to many relation

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

One to one relation

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Many to many relation

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Linking tables

A

the inclusion of a linking table splits the many to many relation into two different one to one relations

17
Q

Primary key and indexing

A

a primary key is automatically indexed within a database
an indexed field is very easily searched and records are quickly retrieved

18
Q

Secondary key and indexing

A

can define a field as a secondary key which the database will then index
makes searching and retrieving records via secondary key much quicker at the cost of increasing the storage space required by the database

19
Q

Data

A

raw and unprocessed (can contain error)
needs processing before we can get any information out of it
can come from automated or human sources

20
Q

How to get data automated sources

A

e.g electronic sensors (weather stations presence detectors web cookies)
produces huge amounts of data cheaply
sensor errors can go unnoticed for a long time
ethical concerns (surveillance anonymity)

21
Q

How to get data human sources

A

e.g census survey
error prone (due to human error)
expensive
difficult to get people to to voluntarily provide private data

22
Q

Turning data to information

A

data needs to be cleaned (removing any errors)
statistical methods/graphical methods can be applied to the data
visualisations are great all about making it easier for the person looking at it
correlation vs causation

23
Q

Storing data

A

easiest way to store data is a table
rows are records
columns are fields

24
Q

Flat file database

A

single table of data
requires no specialised software
portable (flat files are often stored in plain text)
easy to use (requires no specialist training)
large datasets start to become unwieldy (errors can become more prevalent)