Received: from shaked.cc.openu.ac.il (shaked.cc.openu.ac.il [147.233.145.65]) by hub.org (8.8.8/8.8.8) with ESMTP id EAA21747 for ; Tue, 6 Oct 1998 04:55:54 -0400 (EDT) (envelope-from herouth@oumail.openu.ac.il) Received: from [147.233.159.109] (herouth@mac-herouth.pc.openu.ac.il [147.233.159.109]) by shaked.cc.openu.ac.il (8.8.5/8.8.5) with ESMTP id KAA16448; Tue, 6 Oct 1998 10:54:20 +0200 (IST) X-Sender: herouth@shaked.cc.openu.ac.il Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 6 Oct 1998 10:54:06 +0200 To: "Jackson, DeJuan" From: Herouth Maoz Subject: RE: [SQL] Getting datatype before SELECT Cc: pgsql-sql@postgreSQL.org 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