CPMagical CP Library

Problem solution · SQL

Find the Subtasks That Did Not Execute

Find the Subtasks That Did Not Execute: a SQL solution using depth-first search. Learn the idea, check the complexity, and read the full code, with credit to walkccc LeetCode Solutions.

Technique
Depth-first search
Source
walkccc LeetCode Solutions
Length
11 lines
Start with the idea.

Try the problem first. If you get stuck, read the approach below, then write your own solution. The full code is at the bottom.

Approach

Depth-first search

For Find the Subtasks That Did Not Execute, the implementation follows one branch at a time, making it suitable for components, trees, backtracking, or dependency exploration.

  1. Define the state carried into one recursive or stack frame.
  2. Mark or choose the current state before exploring children.
  3. Combine child results or undo the choice when the branch finishes.

Code notes

  • 11 lines of SQL from the credited upstream file 1767.sql.
  • The implementation keeps its working state in language-native values and containers.
  • No explicit loop blocks detected.

Complexity

Count unique states for graph traversal; for backtracking, count the branching factor and maximum depth.

Check the problem constraints before deciding whether this complexity will pass.

Source

Code and credit

This code comes from walkccc LeetCode Solutions by P.-Y. Chen (walkccc) and is used under the MIT licence.

Open problem ↗Original source ↗
Full codeFind the Subtasks That Did Not Execute · SQLSQL
Use this to learn the idea, then write your own version.
WITH RECURSIVE  TaskToSubtask AS (    SELECT task_id, subtasks_count AS subtask_id FROM Tasks    UNION ALL    SELECT task_id, subtask_id - 1 FROM TaskToSubtask    WHERE subtask_id > 1  )SELECT * FROM TaskToSubtaskEXCEPTSELECT * FROM Executed;

Keep practising

Did this explanation save you time? I'm a Grade 11 student building this free library to make difficult algorithms easier to understand.

Buy me a coffee ↗