Re: [GENERAL] Recursive queries

2005-01-26 Thread PFC
Check out ltree http://www.sai.msu.su/~megera/postgres/gist/ltree/ On Tue, 25 Jan 2005 22:03:58 +0100, tmp <[EMAIL PROTECTED]> wrote: I don't think anybody has written the syntactic sugar, but someone did write a function that provides equivalent output. I think it is important that the funcionalit

Re: [GENERAL] Recursive queries

2005-01-26 Thread Martijn van Oosterhout
On Wed, Jan 26, 2005 at 08:52:37AM -0500, Christopher Browne wrote: > By recursive queries, we mean the form defined in SQL3/SQL.1999. > > IBM DB2 uses a syntax like the following; I'd have to rummage around > for extra books to verify standards conformance, but hopefully this > gives the idea...

Re: [GENERAL] Recursive queries

2005-01-26 Thread Christopher Browne
In an attempt to throw the authorities off his trail, kleptog@svana.org (Martijn van Oosterhout) transmitted: > On Mon, Jan 24, 2005 at 05:27:46PM +0100, tmp wrote: >> Are there any plans on implementing support for recursive queries in >> postgresql in the near future? If so: When? >> >> I can s

Re: [GENERAL] Recursive queries

2005-01-25 Thread tmp
> What do you mean by resursive queries? A query can have a subquery > which calls a function which executes another query. That counts as > recursion in my book. What type of recursion are you thinking of? No, recursion is a pretty well defined term. See http://en.wikipedia.org/wiki/Recursion S

Re: [GENERAL] Recursive queries

2005-01-25 Thread tmp
> I don't think anybody has written the syntactic sugar, but someone did > write a function that provides equivalent output. I think it is important that the funcionality lies in the database engine itself: In that way it can more efficiently make use of the optimizer. Also, I think this "recursi

Re: [GENERAL] Recursive queries

2005-01-25 Thread Martijn van Oosterhout
On Tue, Jan 25, 2005 at 08:24:54PM +0100, tmp wrote: > > What do you mean by resursive queries? A query can have a subquery > > which calls a function which executes another query. That counts as > > recursion in my book. What type of recursion are you thinking of? > > SQL:2003 defines a language

Re: [GENERAL] Recursive queries

2005-01-25 Thread Alvaro Herrera
On Tue, Jan 25, 2005 at 07:58:33PM +0100, Martijn van Oosterhout wrote: > On Mon, Jan 24, 2005 at 05:27:46PM +0100, tmp wrote: > > Are there any plans on implementing support for recursive queries in > > postgresql in the near future? If so: When? > > > > I can see there has been some discussion o

Re: [GENERAL] Recursive queries

2005-01-25 Thread Tom Lane
Martijn van Oosterhout writes: > What do you mean by resursive queries? SQL99 "WITH" syntax. See the archives. Andrew Overholt did some work in this direction a year or so back, but didn't get real far ... regards, tom lane ---(end of broadcast)

Re: [GENERAL] Recursive queries

2005-01-25 Thread Martijn van Oosterhout
On Mon, Jan 24, 2005 at 05:27:46PM +0100, tmp wrote: > Are there any plans on implementing support for recursive queries in > postgresql in the near future? If so: When? > > I can see there has been some discussion on the subject in the > developer-group for quite some time ago, but aparently all

Re: [GENERAL] Recursive queries

2005-01-24 Thread Jim C. Nasby
On Mon, Jan 24, 2005 at 06:30:52PM -0500, Christopher Browne wrote: > Quoth tmp <[EMAIL PROTECTED]>: > > Are there any plans on implementing support for recursive queries in > > postgresql in the near future? If so: When? > > > > I can see there has been some discussion on the subject in the > > de

Re: [GENERAL] Recursive queries

2005-01-24 Thread Christopher Browne
Quoth tmp <[EMAIL PROTECTED]>: > Are there any plans on implementing support for recursive queries in > postgresql in the near future? If so: When? > > I can see there has been some discussion on the subject in the > developer-group for quite some time ago, but aparently all thoughts > of recursive

Re: [GENERAL] recursive queries?

2000-04-10 Thread Andrew Schmeder
> Personally, I'm really only interested in something elegant. Meaning I > don't want to mess around with a solution where this broker communicates > with that broker via an n-way blah blah blah. I can maintain literacy > in several tools at once, but not several dozen. Is my best bet simply >