Dataford
Interview QuestionsInterview GuidesExperiencesMock InterviewsPricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan
Avoiding SQL Pitfalls
00:00
5 left

Avoiding SQL Pitfalls

MediumSQL · PostgreSQL

Problem

Explain the difference between a SQL commit and a SQL branch, and what LEFT JOIN and RIGHT JOIN do.

Provide a concise explanation using PostgreSQL terminology and SQL examples. Clarify that COMMIT is a transaction command and that branch is not standard SQL, then demonstrate both join directions with the supplied tables.

Output

  1. Return join_type, branch_id, branch_name, commit_id, and commit_message.
  2. Include results from both join directions, preserving unmatched rows.
  3. Order by join_type, then branch_id, then commit_id, with NULL values last.

Schema

branches
ColumnTypeDescription
branch_idPKINTIdentifier for a branch record
branch_nameVARCHAR(80)Human-readable branch name
commits
ColumnTypeDescription
commit_idPKINTIdentifier for a commit record
branch_idINTBranch associated with the commit
commit_messageVARCHAR(160)Short description of the commit
Tablesbranchescommits
Interviewer

Your question is Avoiding SQL Pitfalls. Start with the requirements and the two tables in the Question tab.

Run and submit as often as you like. When you're ready, talk me through your approach or go straight to the code.

You need to log in / sign up to run or submit.
CodePostgreSQL
Sign up free to run your codeLog inLn 1
Run your query to see results here.