| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rikard Pavelic <rikard(dot)pavelic(at)zg(dot)htnet(dot)hr>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5982: recursive type crashes postgres |
| Date: | 2011-04-15 21:06:28 |
| Message-ID: | BANLkTin2ud7LiKcKCs-USkXdnKnn2b+SqA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Apr 15, 2011 at 3:49 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> I haven't seen anything which seems like a reasonable use case yet,
> myself. If you were *actually* tracking turtles and their
> offspring, that would be a completely worthless data structure. Is
> there really a case where a reference to the ID of an object of like
> type isn't a better solution?
There are lots of use cases for this. I use composite types to
marshal data to the client all the time, and recursive structures are
fairly common in many classic problems. Recursive composites fit the
bill perfectly.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2011-04-15 21:19:55 | Re: BUG #5982: recursive type crashes postgres |
| Previous Message | Rikard Pavelic | 2011-04-15 21:04:03 | Re: BUG #5982: recursive type crashes postgres |