| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | rod(at)iol(dot)ie, PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: SQL - finding next date |
| Date: | 2007-04-12 18:17:19 |
| Message-ID: | 20070412181719.GM15947@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Merlin Moncure escribió:
> my suggestion to return the record in a field as a composite type is a
> non-standard trick (i think...do composite types exist in the sql
> standard?).
I think composite types are in the standard, yes, but they are a bit
different from what we have. I tried to read that part of the standard
a while back and came up blank, it's too filled with strange constructs.
Too closely linked to tables for one thing; there seems to be no notion
of anonymous or standalone types.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dcrespo | 2007-04-12 18:22:42 | Re: Evaluate only one CASE WHEN in a select |
| Previous Message | Merlin Moncure | 2007-04-12 17:38:49 | Re: SQL - finding next date |