Pandas with SQL databases - Time & Space Complexity

Time Complexity: Pandas with SQL databases

O(n)

Understanding Time Complexity

When using pandas to work with SQL databases, it is important to understand how the time taken grows as data size increases.

We want to know how the cost of reading and writing data changes when the database or query size changes.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

import pandas as pd
import sqlite3

conn = sqlite3.connect('example.db')
df = pd.read_sql_query('SELECT * FROM sales WHERE amount > 100', conn)
conn.close()

This code connects to a SQL database, runs a query to get rows where amount is greater than 100, and loads the result into a pandas DataFrame.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The database scans rows to find those matching the condition.
• How many times: Once for each row in the table until all are checked or filtered.

How Execution Grows With Input

As the number of rows in the database grows, the time to scan and filter grows roughly in proportion.

Input Size (n rows)	Approx. Operations
10	About 10 row checks
100	About 100 row checks
1000	About 1000 row checks

Pattern observation: The work grows linearly as the number of rows increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the query and load data grows roughly in direct proportion to the number of rows in the database.

Common Mistake

[X] Wrong: "Reading from a SQL database with pandas is always instant regardless of data size."

[OK] Correct: The database must scan rows to find matches, and pandas must load the data, so bigger data means more time.

Interview Connect

Understanding how pandas interacts with SQL databases and how query size affects time helps you explain data loading performance clearly in real projects.

Self-Check

"What if we add an index on the 'amount' column in the database? How would the time complexity change?"

Practice

1. What is the main purpose of using pandas.read_sql() when working with SQL databases?

easy

A. To read data from a SQL database into a pandas DataFrame

B. To write a pandas DataFrame into a SQL database

C. To create a new SQL database

D. To delete tables from a SQL database

Solution

1. Step 1: Understand the function purpose

   pandas.read_sql() is designed to read data from a SQL query or table.

2. Step 2: Match function to action

   Reading data means loading it into a pandas DataFrame for analysis.

3. Final Answer:

   To read data from a SQL database into a pandas DataFrame -> Option A

4. Quick Check:

   read_sql() = read data [OK]

Hint: read_sql reads data into DataFrame fast [OK]

Common Mistakes:

• Confusing read_sql with to_sql
• Thinking it creates or deletes databases
• Assuming it writes data instead of reading

2. Which of the following is the correct way to create a connection engine to a SQLite database named data.db using SQLAlchemy for pandas?

easy

A. engine = create_engine('sqlite://data.db')

B. engine = create_engine('sqlite:///data.db')

C. engine = create_engine('sqlite:data.db')

D. engine = create_engine('sqlite:/data.db')

Solution

1. Step 1: Recall SQLite connection string format

   SQLite uses the format 'sqlite:///' followed by the database file path.

2. Step 2: Match correct syntax

   engine = create_engine('sqlite:///data.db') uses 'sqlite:///data.db' which is the correct format for a local file.

3. Final Answer:

   engine = create_engine('sqlite:///data.db') -> Option B

4. Quick Check:

   SQLite engine needs three slashes [OK]

Hint: SQLite needs three slashes in connection string [OK]

Common Mistakes:

• Using two slashes instead of three
• Missing slashes or colon
• Confusing with other database connection formats

3. Given the following code, what will be the output of print(df.shape)?

import pandas as pd
from sqlalchemy import create_engine
engine = create_engine('sqlite:///test.db')
df = pd.read_sql('SELECT * FROM users WHERE age > 30', engine)

medium

A. (0, 0) because no data is returned

B. (total_rows_in_users_table, number_of_columns_in_users_table)

C. An error because of incorrect SQL syntax

D. (number_of_rows_with_age_greater_than_30, number_of_columns_in_users_table)

Solution

1. Step 1: Understand the SQL query

   The query selects all columns from 'users' where age is greater than 30, so only matching rows are returned.

2. Step 2: Understand pandas DataFrame shape

   The DataFrame shape is (rows, columns). Rows = filtered rows, columns = all columns from 'users'.

3. Final Answer:

   (number_of_rows_with_age_greater_than_30, number_of_columns_in_users_table) -> Option D

4. Quick Check:

   Filtered rows and all columns = shape [OK]

Hint: DataFrame shape = filtered rows, all columns [OK]

Common Mistakes:

• Assuming all rows are returned
• Thinking shape returns data content
• Confusing SQL syntax with pandas syntax

4. What is wrong with this code snippet that tries to write a DataFrame df to a SQL table named sales?

from sqlalchemy import create_engine
engine = create_engine('sqlite:///sales.db')
df.to_sql('sales', engine)

medium

A. Missing the argument if_exists to handle existing tables

B. The engine connection string is incorrect

C. to_sql cannot write to SQLite databases

D. DataFrame df must be converted to a list first

Solution

1. Step 1: Check to_sql default behavior

   By default, to_sql will raise an error if the table exists unless if_exists is set.

2. Step 2: Identify missing argument

   The code lacks if_exists='replace' or if_exists='append' to avoid errors on existing tables.

3. Final Answer:

   Missing the argument if_exists to handle existing tables -> Option A

4. Quick Check:

   to_sql needs if_exists for existing tables [OK]

Hint: Add if_exists='replace' or 'append' to avoid errors [OK]

Common Mistakes:

• Assuming to_sql always overwrites
• Thinking engine string is wrong
• Believing DataFrame must convert before writing

5. You want to load data from a SQL database into pandas, filter rows where status = 'active', and then write only these filtered rows back to a new SQL table named active_users. Which sequence of commands correctly achieves this?

hard

A. df = pd.read_sql('SELECT * FROM users WHERE status = "active"', engine)
df.to_sql('active_users', engine, if_exists='append')

B. df = pd.read_sql('SELECT * FROM users WHERE status = active', engine)
df.to_sql('active_users', engine)

C. df = pd.read_sql('SELECT * FROM users', engine)
df_filtered = df[df['status'] == 'active']
df_filtered.to_sql('active_users', engine, if_exists='replace')

D. df = pd.read_sql('SELECT * FROM users', engine)
df_filtered = df[df.status = 'active']
df_filtered.to_sql('active_users', engine)

Solution

1. Step 1: Read all data and filter in pandas

   df = pd.read_sql('SELECT * FROM users', engine) df_filtered = df[df['status'] == 'active'] df_filtered.to_sql('active_users', engine, if_exists='replace') reads all users, then filters rows where status equals 'active' using correct pandas syntax.

2. Step 2: Write filtered data with proper if_exists argument

   df = pd.read_sql('SELECT * FROM users', engine) df_filtered = df[df['status'] == 'active'] df_filtered.to_sql('active_users', engine, if_exists='replace') writes filtered data to 'active_users' table, replacing if it exists, avoiding errors.

3. Final Answer:

   df = pd.read_sql('SELECT * FROM users', engine) df_filtered = df[df['status'] == 'active'] df_filtered.to_sql('active_users', engine, if_exists='replace') -> Option C

4. Quick Check:

   Read all, filter in pandas, write with if_exists [OK]

Hint: Filter in pandas, use if_exists='replace' when writing [OK]

Common Mistakes:

• Incorrect SQL syntax in WHERE clause
• Using single equals (=) in pandas filter
• Missing if_exists argument causing errors