RE: [GENERAL] Outer joins

2001-07-13 Thread wsheldah
Lexmark) Subject: RE: [GENERAL] Outer joins Postgres 7.1 does support Left, right & outer joins.  Functions are similar to stored procedures but they cannot return rows.  I think that this limitation is being worked on for the next release (7.2). By the way should there be a 'Postg

Re: [GENERAL] Outer joins

2001-07-13 Thread Tom Lane
eddie iannuccelli <[EMAIL PROTECTED]> writes: > Can anyone confirm me that Postgres 7.1 does not support outer join ? What? It definitely *does* support outer joins. > Are functions similar to classical stored procedure ? Depends on how loose your idea of "similar" is ... a function can't read

RE: [GENERAL] Outer joins

2001-07-13 Thread Trewern, Ben
Title: RE: [GENERAL] Outer joins Postgres 7.1 does support Left, right & outer joins.  Functions are similar to stored procedures but they cannot return rows.  I think that this limitation is being worked on for the next release (7.2). By the way should there be a 'Postgres Features

[GENERAL] Outer joins

2001-07-13 Thread eddie iannuccelli
Can anyone confirm me that Postgres 7.1 does not support outer join ? Are functions similar to classical stored procedure ? thanks -- ** Eddie IANNUCCELLI - tel: 05 61 28 54 44 INRA, Laboratoire de Génétique Cellulaire Chemin de Borde Rouge - Auzev

Re: [GENERAL] outer joins take forever

2001-06-05 Thread Thalis A. Kalfigopoulos
I believe Tom mentioned this sometime ago. If you are picking most of the rows then a seq_scan is preferable to a lookup through the index. In your case you are touching 100% of customer and almost 100% of neicstats, or at least that's what the optimizer thinks. Try vacuum_analyzing the tables

Re: [GENERAL] Outer Joins

2001-01-23 Thread Bruce Momjian
> Bruce Momjian <[EMAIL PROTECTED]> writes: > > Can someone explain why cname and date from table c gets printed in this > > query? > > Say what? > > test=# CREATE TABLE a (id INTEGER, name TEXT, aname TEXT); > CREATE > test=# CREATE TABLE b (id INTEGER, name TEXT, bname TEXT); > CREATE > test=#

Re: [GENERAL] Outer Joins

2001-01-23 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > Can someone explain why cname and date from table c gets printed in this > query? Say what? test=# CREATE TABLE a (id INTEGER, name TEXT, aname TEXT); CREATE test=# CREATE TABLE b (id INTEGER, name TEXT, bname TEXT); CREATE test=# CREATE TABLE c (id IN

Re: [GENERAL] Outer Joins

2001-01-23 Thread Bruce Momjian
Can someone explain why cname and date from table c gets printed in this query? Thanks. > SELECT * FROM a FULL OUTER JOIN b USING (id) > > id | name | aname | name | bname | name | cname |date > +--++--++--+-+ > 1 | Bob | aname1 |

Re: [GENERAL] Outer Joins

2001-01-07 Thread Tom Lane
"Robert B. Easter" <[EMAIL PROTECTED]> writes: UNION JOIN is deprecated >> >> Oh? By whom? > I read it in the SQL spec. ANSI/ISO 9075-2 1999 (final). > It is intended that the following features will be removed at a > later date from a revised version of this part of I

Re: [GENERAL] Outer Joins

2001-01-07 Thread Robert B. Easter
On Sunday 07 January 2001 13:13, Tom Lane wrote: > "Robert B. Easter" <[EMAIL PROTECTED]> writes: > > UNION JOIN is deprecated > > Oh? By whom? > > The reason 7.1 doesn't have it is I didn't have time for it, not that > we don't plan to do it ever. I read it in the SQL spec. ANSI/ISO 9075-2 199

Re: [GENERAL] Outer Joins

2001-01-07 Thread Tom Lane
"Robert B. Easter" <[EMAIL PROTECTED]> writes: > UNION JOIN is deprecated Oh? By whom? The reason 7.1 doesn't have it is I didn't have time for it, not that we don't plan to do it ever. regards, tom lane

Re: [GENERAL] Outer Joins

2001-01-07 Thread Tom Lane
"Robert B. Easter" <[EMAIL PROTECTED]> writes: > Just for the heck of it, I tried to execute all this sql on 7.0.3 and got > this: > psql:join2.sql:23: pqReadData() -- backend closed the channel unexpectedly. > I knew it wouldn't run it, but didn't think it would crash. 7.0 had the beginnings of

Re: [GENERAL] Outer Joins

2001-01-07 Thread Robert B. Easter
On Sunday 07 January 2001 00:53, Robert B. Easter wrote: > Union join: > T1 UNION JOIN T2 > > is not implemented. Nice! :) [snip] > SELECT * FROM a UNION JOIN b; > > ERROR: UNION JOIN is not implemented yet > psql:/home/reaster/sql/join/join.sql:37: ERROR: UNION JOIN is not > implemented yet

Re: [GENERAL] Outer Joins

2001-01-06 Thread Robert B. Easter
On Saturday 06 January 2001 20:21, Tom Lane wrote: > "Robert B. Easter" <[EMAIL PROTECTED]> writes: > > What is the syntax for this? Is there an example I can see/run? > > SQL92 standard. > > See > http://www.postgresql.org/devel-corner/docs/postgres/sql-select.htm > for documentation (such as it

Re: [GENERAL] Outer Joins

2001-01-06 Thread Brett W. McCoy
On Sat, 6 Jan 2001, Robert B. Easter wrote: > What is the syntax for this? Is there an example I can see/run? Should follow standard SQL92 syntax (which, BTW, Oralce doesn't): SELECT * FROM table1 LEFT OUTER JOIN table2 ON (table1.field = table2.field) This will return all rows from table1 ev

Re: [GENERAL] Outer Joins

2001-01-06 Thread Tom Lane
"Robert B. Easter" <[EMAIL PROTECTED]> writes: > What is the syntax for this? Is there an example I can see/run? SQL92 standard. See http://www.postgresql.org/devel-corner/docs/postgres/sql-select.htm for documentation (such as it is). There are some examples in the join regression test, too.

Re: [GENERAL] Outer Joins

2001-01-06 Thread Robert B. Easter
What is the syntax for this? Is there an example I can see/run? On Thursday 04 January 2001 04:30, Poul L. Christiansen wrote: > PostgreSQL 7.1 (which is in beta now) will have outer joins. > > It will probably (and hopefully) be released in Jan./Feb., but the beta > seems quite stable to me. >

[GENERAL] Outer joins

1999-05-24 Thread Kaare Rasmussen
Going through the documentation I can only find little about outer joins. One statement is in the Changes doc about including syntax for outer joins, but there doesn't seem to be implemented any code after that. Is it true that there's no outer joins yet? Any plans? Btw. what is the syntax for ou