SQL database resolvers in GraphQL - Step-by-Step Execution

Concept Flow - SQL database resolvers

GraphQL Query Received

↓

Resolver Function Called

↓

Build SQL Query

↓

Send SQL Query to Database

↓

Database Executes Query

↓

Receive Data from Database

↓

Return Data to GraphQL

↓

GraphQL Response Sent

The flow shows how a GraphQL query triggers a resolver that builds and sends an SQL query to the database, then returns the data back to the client.

Execution Sample

GraphQL

query getUser {
  user(id: 1) {
    id
    name
  }
}

This GraphQL query asks for the user with id 1, requesting their id and name.

Execution Table

Step	Action	SQL Query	Database Response	GraphQL Response
1	Receive GraphQL query
2	Call resolver for 'user'	SELECT id, name FROM users WHERE id = 1;
3	Send SQL query to database	SELECT id, name FROM users WHERE id = 1;
4	Database executes query	SELECT id, name FROM users WHERE id = 1;	{id: 1, name: "Alice"}
5	Receive data from database		{id: 1, name: "Alice"}
6	Return data to GraphQL			{user: {id: 1, name: "Alice"}}
7	Send GraphQL response to client			{user: {id: 1, name: "Alice"}}

💡 GraphQL response sent to client with requested user data.

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
GraphQL Query	null	query getUser { user(id: 1) { id name } }	query getUser { user(id: 1) { id name } }	query getUser { user(id: 1) { id name } }
SQL Query	null	SELECT id, name FROM users WHERE id = 1;	SELECT id, name FROM users WHERE id = 1;	SELECT id, name FROM users WHERE id = 1;
Database Response	null	null	{id: 1, name: "Alice"}	{id: 1, name: "Alice"}
GraphQL Response	null	null	null	{user: {id: 1, name: "Alice"}}

Key Moments - 3 Insights

Why does the resolver build an SQL query instead of returning data directly?

The resolver translates the GraphQL query into an SQL query to fetch data from the database, as shown in execution_table step 2 where the SQL query is built.

What happens if the database returns no data?

If no data is returned, the resolver returns null or an empty response to GraphQL, stopping at step 5 with an empty database response.

How does the resolver know which fields to request from the database?

The resolver reads the requested fields from the GraphQL query and includes only those in the SQL SELECT statement, as seen in step 2 with 'id' and 'name'.

Visual Quiz - 3 Questions

Look at the execution_table, what SQL query is built at step 2?

A SELECT * FROM users;

B SELECT id, name FROM users WHERE id = 1;

C INSERT INTO users VALUES (1, 'Alice');

D DELETE FROM users WHERE id = 1;

💡 Hint

Check the 'SQL Query' column at step 2 in the execution_table.

At which step does the database send back the user data?

A Step 4

B Step 3

C Step 5

D Step 6

💡 Hint

Look at the 'Database Response' column in the execution_table.

If the GraphQL query requested the user's email too, how would the SQL query change at step 2?

A SELECT id, name FROM users WHERE id = 1;

B SELECT email FROM users WHERE id = 1;

C SELECT id, name, email FROM users WHERE id = 1;

D SELECT * FROM users;

💡 Hint

The SQL query includes all requested fields from the GraphQL query, see step 2.

Concept Snapshot

SQL Database Resolvers in GraphQL:
- Resolver receives GraphQL query
- Builds SQL query with requested fields
- Sends SQL query to database
- Receives data from database
- Returns data to GraphQL response
- Enables dynamic data fetching based on query

Full Transcript

When a GraphQL query is received, the resolver function is called. The resolver builds an SQL query that selects only the requested fields from the database. This SQL query is sent to the database, which executes it and returns the data. The resolver then returns this data back to GraphQL, which sends the response to the client. This process allows GraphQL to fetch exactly the data requested by the client from an SQL database.