From: | Herouth Maoz <herouth(at)oumail(dot)openu(dot)ac(dot)il> |
---|---|
To: | "Jackson, DeJuan" <djackson(at)cpsgroup(dot)com> |
Cc: | pgsql-sql(at)postgreSQL(dot)org |
Subject: | RE: [SQL] Getting datatype before SELECT |
Date: | 1998-10-06 08:54:06 |
Message-ID: | l03110700b23f8a4cc903@[147.233.159.109] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
At 18:41 +0200 on 1/10/98, Jackson, DeJuan wrote:
> > The approach is to work on your query, and replace its where clause
> > (or add one if it doesn't have one) with boolean literal 'false'.
> How does this work with joins?
Sorry, I was on vacation...
Shouldn't make any difference. You don't *have* to restrict a join. It
certainly doesn't matter, where the types and lengths of the fields are
important, what the conditions of the join are. Just mention all the table
names. The cartesian product will not be performed, because the condition
is false. Only the types and lengths will be calculated for you.
Herouth
--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Eggenberger | 1998-10-06 09:29:39 | Still the problem with the autoincrement field |
Previous Message | phansen | 1998-10-03 06:50:57 | grouping a ordered list |