On Wed, 22 Mar 2017 10:53:09 -0500
Jeffrey Mattox wrote:
> Isn't it possible to get the same results of a RIGHT JOIN by using
> two selects with a UNION or UNION ALL between them.
Yes. By definition, an outer join is the union of
the rows that meet the matching criteria
After some thinking I came up with this:
First, set up the example (note: no CTE as I am still runnning SQLIte 3.7.14.1):
CREATE temp TABLE stock(id, cid, sid);
CREATE temp TABLE clients(id,name);
CREATE temp TABLE suppliers(id,name);
insert into stock (id) values (1),(2),(3),(4),(5),(6),(7);
ite.org] On
Behalf Of R Smith
Sent: Wednesday, March 22, 2017 9:30 AM
To: sqlite-users@mailinglists.sqlite.org
Subject: Re: [sqlite] RIGHT JOIN! still not supported?
...
The obvious solution was:
SELECT clients.name, suppliers.name
FROM clients
LEFT JOIN stock ON stock.client = clients.id
RIGHT
Unless I misunderstand the desired result, this query would be better formulated
using 2 left joins instead, like this:
SELECT ...
FROM Persons LEFT JOIN Pets ... LEFT JOIN PetAccessories ...
-- Darren Duncan
On 2017-03-22 2:22 AM, Chris Locke wrote:
An interesting discussion of it on
: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im
Auftrag von R Smith
Gesendet: Mittwoch, 22. März 2017 14:30
An: sqlite-users@mailinglists.sqlite.org
Betreff: Re: [sqlite] RIGHT JOIN! still not supported?
On 2017/03/22 9:53 AM, Eric Grange wrote:
For the sake of curiosity, is any
On Wed, Mar 22, 2017 at 9:30 AM, R Smith wrote:
>
> On 2017/03/22 9:53 AM, Eric Grange wrote:
>
>> For the sake of curiosity, is anyone (as in any human) using RIGHT JOIN?
>>
>> Personally I never had a need for a RIGHT JOIN, not because of theoretical
>> or design
...@mailinglists.sqlite.org] Im
Auftrag von R Smith
Gesendet: Mittwoch, 22. März 2017 14:30
An: sqlite-users@mailinglists.sqlite.org
Betreff: Re: [sqlite] RIGHT JOIN! still not supported?
On 2017/03/22 9:53 AM, Eric Grange wrote:
> For the sake of curiosity, is anyone (as in any human) using RIGHT J
On 2017/03/22 9:53 AM, Eric Grange wrote:
For the sake of curiosity, is anyone (as in any human) using RIGHT JOIN?
Personally I never had a need for a RIGHT JOIN, not because of theoretical
or design considerations, but it just never came into my flow of thought
when writing SQL...
I guess
;sqlite-users@mailinglists.sqlite.org>
Subject: Re: [sqlite] RIGHT JOIN! still not supported?
An interesting discussion of it on StackOverflow...
http://stackoverflow.com/questions/689963/does-anyone-use-right-outer-joins
To give one example where a RIGHT JOIN may be useful.
Suppose that there
An interesting discussion of it on StackOverflow...
http://stackoverflow.com/questions/689963/does-anyone-use-right-outer-joins
To give one example where a RIGHT JOIN may be useful.
Suppose that there are three tables for People, Pets, and Pet Accessories.
People may optionally have pets and
For the sake of curiosity, is anyone (as in any human) using RIGHT JOIN?
Personally I never had a need for a RIGHT JOIN, not because of theoretical
or design considerations, but it just never came into my flow of thought
when writing SQL...
I guess some automated SQL query generators could use
What benefit does a RIGHT JOIN give over a LEFT JOIN? What queries are more
natural to write using the first rather than the second?
While I can understand arguments based on simple mirror parity, eg we have < so
we should have > too, lots of other operations don't have mirror syntax either.
Seeing how SQLite was created in 2000, it seems like nobody really
needed this feature for the last 17 years enough in order to actually
implement it.
Last I heard, patches are welcome on this mailing list. Don't keep us waiting.
Kind regards,
Daniel
On 20 March 2017 at 21:09, PICCORO McKAY
Sqlite is public domain, so feel free to add the necessary code, and once
approved, it'll get added to the main code.
Thanks,
Chris
On 20 Mar 2017 8:09 p.m., "PICCORO McKAY Lenz"
wrote:
> i got this
>
> Query Error: RIGHT and FULL OUTER JOINs are not currently
14 matches
Mail list logo