| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Rikard Pavelic" <rikard(dot)pavelic(at)zg(dot)htnet(dot)hr> |
| Cc: | "Merlin Moncure" <mmoncure(at)gmail(dot)com>,<pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #5982: recursive type crashes postgres |
| Date: | 2011-04-15 20:49:24 |
| Message-ID: | 4DA86904020000250003C8CD@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Rikard Pavelic <rikard(dot)pavelic(at)zg(dot)htnet(dot)hr> wrote:
> On 15.4.2011 21:06, Tom Lane wrote:
>> The former.
>>
>> regression=# CREATE TYPE turtle AS
>> (
>> name varchar
>> );
>> CREATE TYPE
>> regression=# ALTER TYPE turtle ADD ATTRIBUTE offspring turtle;
>> ERROR: composite type turtle cannot be made a member of itself
>> regression=#
> Todo item?
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?
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rikard Pavelic | 2011-04-15 21:04:03 | Re: BUG #5982: recursive type crashes postgres |
| Previous Message | Rikard Pavelic | 2011-04-15 20:30:15 | Re: BUG #5982: recursive type crashes postgres |