X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP id 2CBA4D1C95E
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Wed, 19 Nov 2003 07:20:30 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 14230-05
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Wed, 19 Nov 2003 03:20:00 -0400 (AST)
Received: from news.hub.org (news.hub.org [200.46.204.72])
	by svr1.postgresql.org (Postfix) with ESMTP id 53D36D1B538
	for <pgsql-sql@postgresql.org>; Wed, 19 Nov 2003 03:19:59 -0400 (AST)
Received: from news.hub.org (news.hub.org [200.46.204.72])
	by news.hub.org (8.12.9/8.12.9) with ESMTP id hAJ7JwO0099188
	for <pgsql-sql@postgresql.org>; Wed, 19 Nov 2003 07:19:59 GMT
	(envelope-from news@news.hub.org)
Received: (from news@localhost)
	by news.hub.org (8.12.9/8.12.9/Submit) id hAJ6uqdN094171
	for pgsql-sql@postgresql.org; Wed, 19 Nov 2003 06:56:52 GMT
From: "Randolf Richardson, DevNet SysOp 29" <rr@8x.ca>
X-Newsgroups: comp.databases.postgresql.sql
Subject: Re: SOLVED: Emulating 'connect by prior' using stored proc
Date: Wed, 19 Nov 2003 06:56:52 +0000 (UTC)
Organization: Inter-Corporate Computer & Network Services, Inc.
Lines: 26
Message-ID: <Xns9437E76B976E3rr8xca@200.46.204.72>
References: 
 <B7AD8B4B4A337741B62E633B4827ADD932D5CD@svrexc02.aolau.ops.au.office.aol.com>
X-Complaints-To: usenet@news.hub.org
User-Agent: Xnews/5.04.25
X-Face: 
 +kXh]<cm0}l<Fvzd*?E]I7=Ug!X`>8'{:R`HzXla-aT~$s8a+C)k/B%RBr$_3sP`[kA}cl7#mD^9Z:oM`HpoC_kUEH['RZ*Ob%pz\ww^q&x)~zc`.xd]VQ4WN/3t2nS-<I>BvI%LF\B4:\9$EI:/|<)`?8I_;
	xzG@SOYFir/gk_eB4"Rl43-h%)8O0sR$b&Mp3XHR(0j=
X-Face-Author: Randolf Richardson (composed with Adobe Photoshop)
To: pgsql-sql@postgresql.org
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200311/239
X-Sequence-Number: 16054

[sNip]
> It's the same in this case. The tree building stuff only ever looks down
> so the level returned in the query results will start at 1 no matter
> where you enter your tree.  In our case we could enter the tree at
> 'node' 100 and get the tree below that but the function will start at 1
> because we only interested in the data below not the entry point and not
> where in the tree we entered.

    	Thanks.  That's excellent news!  =)

> As in the solution if you really want to start it at 5 then set that as
> the value of your second parameter.

    	Interesting.  Although I don't have an immediate need for this, I'm 
sure it could be useful when storing the results of multiple queries of this 
nature in a temporary table.

-- 
Randolf Richardson - rr@8x.ca
Inter-Corporate Computer & Network Services, Inc.
Vancouver, British Columbia, Canada
http://www.8x.ca/

This message originated from within a secure, reliable,
high-performance network ... a Novell NetWare network.