From: Robert Treat <xzilla@users.sourceforge.net>
To: Josh Berkus <josh@agliodbs.com>
To: Andrew Rawnsley <ronz@ravensfield.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Nested Sets WAS: column size too large, is this a bug?
Date: Tue, 30 Mar 2004 15:06:08 -0500
Message-ID: <200403301506.08882.xzilla@users.sourceforge.net> (raw)
In-Reply-To: <200403300838.50538.josh@agliodbs.com>
References: <082D0538-7E86-11D8-8B9C-000A95AB8896@quotefx.net>
<200403300920.27739.xzilla@users.sourceforge.net>
<200403300838.50538.josh@agliodbs.com>
On Tuesday 30 March 2004 11:38, Josh Berkus wrote:
> Robert,
>
> > If you search the pgsql-sql archives you'll find some helpful threads on
> > using nested sets in PostgreSQL, one in particular I was involved with
> > was a generic "move_tree" function that enabled moving a node from one
> > branch to another.
>
> I have to admit to failing to follow -SQL over the last few months. This
> list and Hackers are pretty much the only ones I read all of.
>
> Maybe I should get back on -SQL and we can compare move_tree functions :-)
>
> Did yours use a temp table, or some other means?
Nope, Greg Mullane and I worked out the math and came up with an algorithm of
sorts that we could apply to the tree when moving elements.
<digs a little>
http://archives.postgresql.org/pgsql-sql/2002-11/msg00355.php
Seemed to work though someone else had posted yet another version after
ours... and in fact the one posted is not exactly what I use now either :-)
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: xzilla@users.sourceforge.net, josh@agliodbs.com, ronz@ravensfield.com
Subject: Re: Nested Sets WAS: column size too large, is this a bug?
In-Reply-To: <200403301506.08882.xzilla@users.sourceforge.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox