Received: from localhost (pluto.hub.org [200.46.204.4]) by postgresql.org (Postfix) with ESMTP id 9A3DA9F94EA for ; Wed, 15 Nov 2006 14:45:43 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.4]) (amavisd-new, port 10024) with ESMTP id 66171-10 for ; Wed, 15 Nov 2006 14:45:38 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from talk.nabble.com (www.nabble.com [72.21.53.35]) by postgresql.org (Postfix) with ESMTP id 941B49F946B for ; Wed, 15 Nov 2006 14:45:39 -0400 (AST) Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1GkPlS-0004ZP-Fr for pgsql-sql@postgresql.org; Wed, 15 Nov 2006 10:45:38 -0800 Message-ID: <7363779.post@talk.nabble.com> Date: Wed, 15 Nov 2006 10:45:38 -0800 (PST) From: chrisj To: pgsql-sql@postgresql.org Subject: recursive SQL and with clause MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: chrisj.wood@sympatico.ca X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/158 X-Sequence-Number: 26810 I was just wondering when we could reasonably expect recursive SQL to be added to Postgres? I saw some posts from 2004 that made it sound like it was imminent, but I guess something went wrong? I believe the WITH clause is a pre-requisite for recursive SQL, however I do find the WITH clause also very useful in decomposing very complex SQL into understandable chunks. -- View this message in context: http://www.nabble.com/recursive-SQL-and-with-clause-tf2638088.html#a7363779 Sent from the PostgreSQL - sql mailing list archive at Nabble.com.