Received: from hu.tm.ee (ppp907.tele2.ee [212.107.37.207]) by hub.org (8.9.3/8.9.3) with ESMTP id EAA52029; Thu, 3 Feb 2000 04:59:10 -0500 (EST) (envelope-from hannu@tm.ee) Received: from tm.ee (localhost [127.0.0.1]) by hu.tm.ee (Postfix) with ESMTP id 9CF443987; Thu, 3 Feb 2000 12:06:09 +0200 (EET) Sender: hannu@hu.tm.ee Message-ID: <38995311.AA81CA4A@tm.ee> Date: Thu, 03 Feb 2000 12:06:09 +0200 From: Hannu Krosing Organization: Trust-O-Matic =?iso-8859-1?Q?O=DC?= X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13-7mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Momjian Cc: chris@bitmead.com, "pgsql-hackers@postgreSQL.org" , pgsql-sql@postgreSQL.org, pgsql-general@postgreSQL.org Subject: Re: [HACKERS] Re: [GENERAL] Proposed Changes to PostgreSQL References: <200002030257.VAA00457@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Bruce Momjian wrote: > > > Bruce Momjian wrote: > > > > > So the field is created on the fly to show what table it came from. > > > Seems like a good idea, though implementing another usually-invisible > > > column will be tough. > > > > What problems do you forsee? > > Well, it is usually pretty strange to carry around a column that doesn't > exist through all the code and finally contruct it at the end. I would > suspect something in the rewrite system could do that pretty easily, > though. That is the direction I would go with that. > Oracle has a ROWNR (IIRC) pseudo-column that is added in th every end of query and is a convienient way to put numbers on report rows (among other things). ------------ Hannu