Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id SAA43255 for ; Mon, 27 Sep 1999 18:47:04 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id SAA27651; Mon, 27 Sep 1999 18:45:35 -0400 (EDT) To: Bruce Momjian cc: Howie , pgsql-sql@hub.org Subject: Re: [SQL] table aliasing problem with 6.5... In-reply-to: Your message of Mon, 27 Sep 1999 13:44:19 -0400 (EDT) <199909271744.NAA09308@candle.pha.pa.us> Date: Mon, 27 Sep 1999 18:45:35 -0400 Message-ID: <27649.938472335@sss.pgh.pa.us> From: Tom Lane Bruce Momjian writes: > OK, I have added an elog(NOTICE) for this behavior: > test=> select * from pg_language; > lanname |lanispl|lanpltrusted|lanplcallfoid|lancompiler > --------+-------+------------+-------------+-------------- > internal|f |f | 0|n/a > lisp |f |f | 0|/usr/ucb/liszt > C |f |f | 0|/bin/cc > sql |f |f | 0|postgres > (4 rows) > test=> select pg_language.*; --> NOTICE: Auto-creating query reference to table pg_language > lanname |lanispl|lanpltrusted|lanplcallfoid|lancompiler > --------+-------+------------+-------------+-------------- > internal|f |f | 0|n/a > lisp |f |f | 0|/usr/ucb/liszt > C |f |f | 0|/bin/cc > sql |f |f | 0|postgres > (4 rows) > I am interested in comments about my wording, and this behavour. I think this is a fine idea, but that wording might not be much help to novices. Maybe "Adding missing FROM-clause entry for pg_language", or some such? In a situation where you've got subselects, it may not be immediately obvious which FROM list the entry got added to. I can't think of any simple way of identifying that, however :-( regards, tom lane