Received: from shaked.cc.openu.ac.il (shaked.cc.openu.ac.il [147.233.145.65]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA57452 for ; Mon, 6 Sep 1999 11:34:58 -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.8/8.8.8) with ESMTP id RAA11702; Mon, 6 Sep 1999 17:34:31 +0200 (IST) X-Sender: herouth@shaked.cc.openu.ac.il Message-Id: In-Reply-To: <37C95508.B50F49BD@AVALON.at> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 6 Sep 1999 18:36:36 +0300 To: avalon@teleweb.at, pgsql-sql@postgreSQL.org From: Herouth Maoz Subject: Re: [SQL] SELECT multiple tables with same fields At 18:43 +0300 on 29/08/1999, Dipl.-Ing. Thomas Schallar wrote: > But if I add fields, than I have to add > them to each of the SELECT statements also, that they won't be missed > off. That's boaring und faulty. One may argue about that. I was told in the past never to use * except when "just checking", i.e. when running something ad-hoc in psql. In applications, it is always recommended to write the names of the fields explicitly, which makes sure you don't include fields which are not really needed, and you know exactly what you got back and why you got it. The minute you use an equijoin, you have one field which is truly redundant, not just by name, but also in value. I think that writing a query is something you do once, but many many redundant bytes will be transmitted as a result of being lazy during the writing of the query. Herouth -- Herouth Maoz, Internet developer. Open University of Israel - Telem project http://telem.openu.ac.il/~herutma