Re: [sqlite] Full outer joins

2014-10-24 Thread Steinar Midtskogen
Richard Hipp writes: > In 14 years, you are the first person to ask for them. That tells me that > probably not many people would use them even if we did put them in. I've only written one program using sqlite a few years ago, and I had to make an ugly workaround using UNIONs

Re: [sqlite] Full outer joins

2014-10-22 Thread Stephen Chrzanowski
Saying I 'would like this type of join' is something I say very lightly. By that I mean it'd be good to see them, but, really, I'm not going to put any pressure on anyone to get it implemented. I'd been using these joins in SQL2K for years before I found out about SQLite and a lot of what I was

Re: [sqlite] Full outer joins

2014-10-22 Thread Paul Sanderson
Really!! I can accept that it would not be needed as often as other joins but I can imagine that anyone who wrtes software that populates databases and who subsequently changes their software or needs to benchmark against some other datasource would find this useful. Cheers Paul On 22 October

Re: [sqlite] Full outer joins

2014-10-21 Thread dave
> -Original Message- > From: sqlite-users-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Richard Hipp > Sent: Tuesday, October 21, 2014 6:59 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] Full outer joins > >

Re: [sqlite] Full outer joins

2014-10-21 Thread Keith Medcalf
Ooops. This can be further simplified as: select rowid from a where rowid not in b union all select rowid from b where rowid not in a; >>It looks hairy but here's what it's doing. Given tables A,B: > >>1. Do the regular join (all rows with matches in both A and B) >>2. Find rows in A that

Re: [sqlite] Full outer joins

2014-10-21 Thread Keith Medcalf
>It looks hairy but here's what it's doing. Given tables A,B: >1. Do the regular join (all rows with matches in both A and B) >2. Find rows in A that aren't in B >3. Find rows in B that aren't in A >4. Concatenate those 3 queries together with UNION ALL will be the same as A UNION ALL B, which

Re: [sqlite] Full outer joins

2014-10-21 Thread Richard Hipp
On Tue, Oct 21, 2014 at 7:12 PM, Paul Sanderson < sandersonforens...@gmail.com> wrote: > out of interest why are > full out joins not supported? > In 14 years, you are the first person to ask for them. That tells me that probably not many people would use them even if we did put them in. --

Re: [sqlite] Full outer joins

2014-10-21 Thread David King
> I want to find the rows that dont appear in both tables. So I think I > need a full outer join which I understand is not supported by SQLite > I have seen this which gives an alternative, but it seems very complex > http://en.wikipedia.org/wiki/Join_%28SQL%29#Full_outer_join > Is there an easier

[sqlite] Full outer joins

2014-10-21 Thread Paul Sanderson
I have two tables from two versions of the same database each table has an integer id primary key I want to find the rows that dont appear in both tables. So I think I need a full outer join which I understand is not supported by SQLite I have seen this which gives an alternative, but it seems