Thanks all for the input. My knowledge from nearly 20 years ago is a bit rusty when it came to material like this. Just adding "LEFT JOIN" instead of just "JOIN" has my query working as I need it to. This type of result set isn't something I regularly perform.
On Wed, Dec 6, 2017 at 4:41 AM, Simon Slavin <slav...@bigfraud.org> wrote: > On 6 Dec 2017, at 9:36am, Jean-Luc Hainaut <jean-luc.hain...@unamur.be> > wrote: > > > Actually, the left outer join is sufficient to execute all the outer > join operators: > > > > - right outer join: just swap the "from" arguments > > > > - full outer joins: union of left and right outer joins > > I never realised that. It’s clever. And it’s also a cheap way to > implement FULL JOINs. > > Not optimized, but it simple, and changes "can’t do" to "can do". Thanks. > > Simon. > _______________________________________________ > sqlite-users mailing list > email@example.com > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list firstname.lastname@example.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users