Database in everyday apps (social media, banking) in Intro to Computing - Flowchart & Logic Diagram

Process Overview

A database is like a digital filing cabinet that stores information for apps you use every day, like social media and banking. This flowchart shows how data is stored, retrieved, and updated to keep your app working smoothly.

Flowchart

Rectangle

↓

Rectangle

↓

Rectangle

↓

Rectangle

No path:↓

Rectangle

↓

Rectangle

↓

Rectangle

This flowchart shows how an app interacts with a database: the app asks for data, the database checks if it has it, then either sends it or fetches and stores it before sending.

Step-by-Step Trace - 6 Steps

Step 1: User opens the social media app.

Step 2: App sends a request to the database for user posts.

Step 3: Database checks if posts are stored.

Step 4: Posts are found in the database (Yes branch).

Step 5: Database sends posts data back to the app.

Step 6: User sees posts on the app screen.

Diagram

 +-----------------+       +-----------------+       +-----------------+
 |                 |       |                 |       |                 |
 |     User's      |       |      App        |       |    Database     |
 |    Device       |       | (Social Media)  |       |                 |
 |                 |       |                 |       |                 |
 +--------+--------+       +--------+--------+       +--------+--------+
          |                         |                         |
          | Open app                |                         |
          |------------------------>|                         |
          |                         | Request posts data      |
          |                         |------------------------>|
          |                         |                         | Check if data exists
          |                         |                         |------------------>
          |                         |                         | Yes: Retrieve data
          |                         |                         |<------------------
          |                         | Receive data            |
          |                         |<------------------------|
          | Display posts           |                         |
          |<------------------------|                         |

This diagram shows the three main parts: the user's device, the app, and the database. The app asks the database for data, the database checks and sends it back, and the app shows it to the user.

Flowchart Quiz - 3 Questions

What happens if the database does NOT have the requested data?

A It fetches data from an external source and stores it.

B It sends an error message to the app.

C It ignores the request.

D It deletes old data.

Key Result

Databases act like organized storage that apps ask for data from, ensuring quick and reliable access to information users need.

Practice

1. What is the main purpose of a database in apps like social media or banking?

easy

A. To send emails to users automatically

B. To store and organize information so it can be easily found and used

C. To control the app's colors and fonts

D. To create graphics and animations for the app

Solution

1. Step 1: Understand what apps need

   Apps like social media and banking need to keep lots of information safe and easy to find.

2. Step 2: Role of a database

   A database stores and organizes this information in tables, like a digital filing cabinet.

3. Final Answer:

   To store and organize information so it can be easily found and used -> Option B

4. Quick Check:

   Database = store and organize info [OK]

Hint: Databases hold data, not design or emails [OK]

Common Mistakes:

• Confusing database with app design features
• Thinking database sends emails
• Mixing database with app styling

2. Which of the following is the correct way to describe a table in a database?

easy

A. A program that runs the app on your phone

B. A folder on your computer where files are saved

C. A place where data is stored in rows and columns, like a spreadsheet

D. A list of colors used in the app design

Solution

1. Step 1: Recall what a table is

   A table in a database organizes data in rows and columns, similar to a spreadsheet.

2. Step 2: Compare options

   Only 'A place where data is stored in rows and columns, like a spreadsheet' correctly describes this; others describe unrelated things.

3. Final Answer:

   A place where data is stored in rows and columns, like a spreadsheet -> Option C

4. Quick Check:

   Table = rows and columns [OK]

Hint: Think spreadsheet when you hear 'table' in databases [OK]

Common Mistakes:

• Confusing tables with app programs
• Mixing tables with computer folders
• Thinking tables are design elements

3. Consider a social media app database table named Users with columns UserID, Name, and Age. If the table has these rows:

UserID | Name   | Age
1      | Alice  | 25
2      | Bob    | 30
3      | Carol  | 22

What will be the result of a query that finds all users older than 23?

medium

A. Alice and Bob

B. Bob and Carol

C. Alice, Bob, and Carol

D. Only Carol

Solution

1. Step 1: Identify users older than 23

   Check each user's age: Alice (25) > 23, Bob (30) > 23, Carol (22) ≤ 23.

2. Step 2: List matching users

   Alice and Bob meet the condition; Carol does not.

3. Final Answer:

   Alice and Bob -> Option A

4. Quick Check:

   Age > 23 = Alice, Bob [OK]

Hint: Filter by age > 23 carefully [OK]

Common Mistakes:

• Including Carol who is 22
• Missing Bob who is 30
• Selecting all users without filtering

4. A banking app database has a table Accounts with columns AccountID, Balance. The following SQL query is written:

SELECT AccountID, Balance FROM Accounts WHERE Balance > 1000

But the app returns an error. What is the most likely mistake?

medium

A. The column Balance does not exist or is misspelled

B. The SQL query is missing a semicolon at the end

C. The table name Accounts is misspelled

D. The query should use SELECT * FROM Accounts instead

Solution

1. Step 1: Check query syntax

   The query syntax is correct and semicolon is optional in many systems.

2. Step 2: Verify column names

   If the app errors, likely the column Balance is misspelled or missing in the table.

3. Final Answer:

   The column Balance does not exist or is misspelled -> Option A

4. Quick Check:

   Column name error causes query failure [OK]

Hint: Check column names carefully for typos [OK]

Common Mistakes:

• Assuming missing semicolon causes error
• Thinking table name is wrong without checking
• Believing SELECT * fixes column errors

5. A social media app wants to show a list of friends for a user. The database has two tables:

Users(UserID, Name)
Friends(UserID1, UserID2)

If UserID1 and UserID2 represent friend pairs, which SQL query correctly finds all friends of user with UserID = 5?

hard

A. SELECT Name FROM Users WHERE UserID IN (SELECT UserID2 FROM Friends WHERE UserID1 = 5)

B. SELECT Name FROM Users WHERE UserID = 5

C. SELECT Name FROM Users WHERE UserID IN (SELECT UserID1 FROM Friends WHERE UserID2 = 5)

D. SELECT Name FROM Users WHERE UserID IN (SELECT UserID1 FROM Friends WHERE UserID2 = 5) OR UserID IN (SELECT UserID2 FROM Friends WHERE UserID1 = 5)

Solution

1. Step 1: Understand friend pairs

   Friends table stores pairs (UserID1, UserID2) meaning both are friends.

2. Step 2: Find all friends of UserID 5

   Friends can appear as UserID1 or UserID2, so query must check both sides.

3. Step 3: Analyze options

   SELECT Name FROM Users WHERE UserID IN (SELECT UserID1 FROM Friends WHERE UserID2 = 5) OR UserID IN (SELECT UserID2 FROM Friends WHERE UserID1 = 5) checks both UserID1 and UserID2 for 5, correctly finding all friends.

4. Final Answer:

   SELECT Name FROM Users WHERE UserID IN (SELECT UserID1 FROM Friends WHERE UserID2 = 5) OR UserID IN (SELECT UserID2 FROM Friends WHERE UserID1 = 5) -> Option D

5. Quick Check:

   Check both friend columns for user 5 [OK]

Hint: Friends can be in either column, check both [OK]

Common Mistakes:

• Checking only one side of friend pairs
• Selecting user 5 instead of their friends
• Using wrong columns in subqueries