| From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com>, Andrew Rawnsley <ronz(at)ravensfield(dot)com>, Qing Zhao <qzhao(at)quotefx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: column size too large, is this a bug? |
| Date: | 2004-03-30 14:20:27 |
| Message-ID: | 200403300920.27739.xzilla@users.sourceforge.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sunday 28 March 2004 14:25, Josh Berkus wrote:
> Andrew,
>
> > I used to use the connect-by patch, but have since rewritten everything
> > to use a nested set model.
>
> Cool! You're probably the only person I know other than me using nested
> sets in a production environment.
You cut me deep there Josh, real deep. :-)
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.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-03-30 16:38:50 | Re: Nested Sets WAS: column size too large, is this a bug? |
| Previous Message | Rob Fielding | 2004-03-30 12:54:36 | Cleanup query takes along time |