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
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...
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
> 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
> 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
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
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
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)
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
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 queries has been stalled. :-(
Regards
-
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
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
I have a database with the following fields:
product_id INTEGER
parent_id INTEGER
nameVARCHAR(64)
The idea is that it will store a tree of products and its subproducts. Any
row whose parent_id is NULL will be assumed to be a root product (i.e. top
level).
This means
Hi all,
I have a question that probably is more apropriate for pgsql-dummies but
since I use postgres and don't know what list would be more
apropriate... here goes:
I have some data that I want to be able to search by geographic location.
The geographic locations are stored in a table with a r
> 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
>
Now and again, I find myself wanting to store data in some kind of
variable-level hierarchy. To take a familiar example, let's say the
directory structure on my computer.
So I start to do something like:
CREATE SEQUENCE directory_id_seq;
CREATE TABLE directory {
parent INTEGER,
16 matches
Mail list logo
