The case of the missing tuple: teaching the SQL outer-join operator to undergraduate information systems students

  • Authors:
  • Victor Matos;Rebecca Grasser;Paul Jalics

  • Affiliations:
  • Cleveland State University, Cleveland OH;Cleveland State University, Cleveland OH;Cleveland State University, Cleveland OH

  • Venue:
  • Journal of Computing Sciences in Colleges
  • Year:
  • 2006

Quantified Score

Hi-index 0.00

Visualization

Abstract

Once students have mastered basic database querying with SQL, the next step for the instructor is to present operators that can extract complex information from multiple tables. The relational database left-outer-join (LOJ) expression (T1▹T2) is used to merge two tables, say T1 and T2, using any given condition. Unlike regular database joins, when records from the first table (T1) fail to match records in the second table (T2) the LOJ operator retains each of those T1 tuples and adds an appropriate number of "null" values to compensate for the missing contribution of T2 records. In spite of its relatively simple definition and frequency in everyday common problems, we have observed that novice database students oftentimes have difficulties in understanding and properly using this technique. In this paper, we discuss three functionally equivalent versions of the left-outer-join operator to allow multiple ways of presenting the material and to show students a single data extraction problem from three viewpoints. We have developed an empirical evaluation of perceived difficulty and manageability of those versions. A simple performance analysis is conducted to determine the relative merits of each alternative.