User feedback collection in No-Code - Time & Space Complexity

Time Complexity: User feedback collection

O(1)

Understanding Time Complexity

When collecting user feedback in a database, it's important to understand how the time to save or retrieve feedback grows as more users submit their opinions.

We want to know how the process scales when more feedback entries are added.

Scenario Under Consideration

Analyze the time complexity of the following process to save user feedback.

// Pseudocode for saving user feedback
function saveFeedback(feedbackList, newFeedback) {
  feedbackList.append(newFeedback);
  return feedbackList;
}
    

This code adds a new feedback entry to the existing list of feedbacks.

Identify Repeating Operations

Look for any repeated actions that happen as more feedback is collected.

• Primary operation: Adding one new feedback entry to the list.
• How many times: Once per new feedback submission.

How Execution Grows With Input

Adding a new feedback entry takes about the same time no matter how many feedbacks are already stored.

Input Size (n)	Approx. Operations
10	1 append operation
100	1 append operation
1000	1 append operation

Pattern observation: The time to add feedback stays about the same regardless of how many feedbacks exist.

Final Time Complexity

Time Complexity: O(1)

This means adding a new feedback takes a constant amount of time, no matter how many feedback entries are already stored.

Common Mistake

[X] Wrong: "Adding feedback takes longer as the list grows because it has to check all previous feedbacks."

[OK] Correct: Adding to the end of a list usually just places the new item without checking others, so time stays constant.

Interview Connect

Understanding how simple operations like adding feedback scale helps you explain database efficiency clearly and confidently in real-world situations.

Self-Check

"What if we had to search through all feedbacks to check for duplicates before adding? How would the time complexity change?"

Practice

1. What is the main purpose of collecting user feedback in a database?

easy

A. To delete old user data automatically

B. To store opinions that help improve products

C. To increase the size of the database

D. To prevent users from accessing the system

Solution

1. Step 1: Understand the role of user feedback

   User feedback is collected to learn what users think about a product or service.

2. Step 2: Connect feedback to product improvement

   Storing opinions helps teams improve features and fix problems.

3. Final Answer:

   To store opinions that help improve products -> Option B

4. Quick Check:

   User feedback = product improvement [OK]

Hint: Feedback stores opinions to improve products [OK]

Common Mistakes:

• Thinking feedback deletes data
• Confusing feedback with database size
• Assuming feedback blocks user access

2. Which of the following is the correct way to define a feedback table with fields for user name, rating, comment, and date?

easy

A. MAKE TABLE feedback (user_name CHAR, rate FLOAT, comment VARCHAR, date_time DATETIME);

B. CREATE feedback TABLE (user TEXT, stars TEXT, note TEXT, time TEXT);

C. TABLE feedback CREATE (name STRING, score NUMBER, feedback STRING, day DATE);

D. CREATE TABLE feedback (username TEXT, rating INTEGER, comment TEXT, date DATE);

Solution

1. Step 1: Identify correct SQL syntax for table creation

   The correct syntax starts with CREATE TABLE, followed by table name and fields with types.

2. Step 2: Match field names and types to feedback data

   username as TEXT, rating as INTEGER, comment as TEXT, and date as DATE are appropriate.

3. Final Answer:

   CREATE TABLE feedback (username TEXT, rating INTEGER, comment TEXT, date DATE); -> Option D

4. Quick Check:

   CREATE TABLE + fields = CREATE TABLE feedback (username TEXT, rating INTEGER, comment TEXT, date DATE); [OK]

Hint: CREATE TABLE with field names and types [OK]

Common Mistakes:

• Using wrong SQL keywords like MAKE or TABLE CREATE
• Incorrect data types for fields
• Wrong order of keywords

3. Given the feedback table below, what will this query return?

SELECT username, rating FROM feedback WHERE rating >= 4;

Table data:
username | rating | comment | date
alice | 5 | Great! | 2024-06-01
bob | 3 | Okay | 2024-06-02
carol | 4 | Good | 2024-06-03

medium

A. [{"username": "alice", "rating": 5}, {"username": "carol", "rating": 4}]

B. [{"username": "bob", "rating": 3}]

C. [{"username": "alice", "rating": 5}, {"username": "bob", "rating": 3}]

D. []

Solution

1. Step 1: Understand the query condition

   The query selects username and rating where rating is greater than or equal to 4.

2. Step 2: Check table rows against condition

   alice has rating 5 (>=4), carol has rating 4 (>=4), bob has rating 3 (<4).

3. Final Answer:

   [{"username": "alice", "rating": 5}, {"username": "carol", "rating": 4}] -> Option A

4. Quick Check:

   rating >= 4 returns alice and carol [OK]

Hint: Filter ratings >= 4 to get alice and carol [OK]

Common Mistakes:

• Including users with rating less than 4
• Selecting wrong columns
• Misreading >= as >

4. You wrote this query to add feedback but it gives an error:

INSERT INTO feedback (username, rating, comment, date) VALUES ('dave', 'five', 'Nice', '2024-06-04');

What is the likely cause of the error?

medium

A. The rating value 'five' is a string, but rating expects a number

B. The date format is incorrect

C. The comment field cannot contain text

D. The username field is missing

Solution

1. Step 1: Check data types in the INSERT statement

   Rating is expected as a number, but 'five' is a text string.

2. Step 2: Identify mismatch causing error

   Using a string where a number is expected causes a type error in the database.

3. Final Answer:

   The rating value 'five' is a string, but rating expects a number -> Option A

4. Quick Check:

   Rating type mismatch = The rating value 'five' is a string, but rating expects a number [OK]

Hint: Match data types exactly in INSERT statements [OK]

Common Mistakes:

• Using text instead of number for rating
• Assuming date format is wrong without checking
• Thinking comment cannot have text

5. You want to find all feedback comments from users who gave a rating less than 3 and sort them by date newest first. Which query achieves this?

hard

A. SELECT username, comment FROM feedback WHERE rating < 3 ORDER BY date ASC;

B. SELECT comment FROM feedback WHERE rating >= 3 ORDER BY date ASC;

C. SELECT username, comment FROM feedback WHERE rating < 3 ORDER BY date DESC;

D. SELECT username, comment FROM feedback ORDER BY rating DESC, date ASC;

Solution

1. Step 1: Filter feedback with rating less than 3

   The WHERE clause should use rating < 3 to get low ratings.

2. Step 2: Sort results by date descending

   ORDER BY date DESC sorts newest feedback first.

3. Final Answer:

   SELECT username, comment FROM feedback WHERE rating < 3 ORDER BY date DESC; -> Option C

4. Quick Check:

   Filter rating < 3 + ORDER BY date DESC = SELECT username, comment FROM feedback WHERE rating < 3 ORDER BY date DESC; [OK]

Hint: Use WHERE rating < 3 and ORDER BY date DESC [OK]

Common Mistakes:

• Using wrong comparison operator for rating
• Sorting dates ascending instead of descending
• Selecting wrong columns