Re: Nested Sets WAS: column size too large, is this a bug?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Andrew Rawnsley <ronz(at)ravensfield(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Nested Sets WAS: column size too large, is this a bug?
Date: 2004-03-30 16:38:50
Message-ID: 200403300838.50538.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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?

--
Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Josh Berkus 2004-03-30 16:43:01 Re: [ADMIN] Raw vs Filesystem
Previous Message Robert Treat 2004-03-30 14:20:27 Re: column size too large, is this a bug?