Received: from news.tht.net (news.hub.org [216.126.91.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f35FPA841504 for ; Thu, 5 Apr 2001 11:25:10 -0400 (EDT) (envelope-from news@news.tht.net) Received: (from news@localhost) by news.tht.net (8.11.1/8.11.1) id f35FGKH44767 for pgsql-sql@postgresql.org; Thu, 5 Apr 2001 11:16:20 -0400 (EDT) (envelope-from news) From: "Gordon A. Runkle" X-Newsgroups: comp.databases.postgresql.sql Subject: Re: Re: UNION in a VIEW? Date: Thu, 05 Apr 2001 11:21:36 -0400 Organization: Integrated Dynamics, Inc. Lines: 18 Message-ID: <9ai25s$1bmf$1@news.tht.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: scrappy@hub.org User-Agent: Pan/0.9.6 (Unix) X-No-Productlinks: Yes To: pgsql-sql@postgresql.org X-Archive-Number: 200104/83 X-Sequence-Number: 2423 In article , "Josh Berkus" wrote: > Tom ... and I realize that we're talking about features for version 7.3 > or later ... a direct way to approach it would be to do a push-down on > simple UNION views, and to do output filtering on UNION views wich > contain a CASE, any subselect, or CAST expression (or similar) on the > filtered columns. This sounds right to me. (Which is easy for me to say, as I'm not the one with the know-how to actually do it!) I'd like to see cases like my example (simple joins) work, since that's the main reason for doing the UNION in the first place. I came up with a data workaround in my case, so I'm set for now) Gordon. -- It doesn't get any easier, you just go faster. -- Greg LeMond