| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Polymorphic arguments and composite types |
| Date: | 2007-10-05 17:51:30 |
| Message-ID: | 1191606690.4223.426.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2007-10-05 at 13:18 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > I'll look at documenting that.
>
> I think the problem here is you've not bothered to read the manual,
> because all of these behaviors *are* documented; two of them are
> furthermore required by the SQL standard.
Your thoughts aren't correct, but why so touchy?
There is no comment in the manual here
http://developer.postgresql.org/pgdocs/postgres/arrays.html#AEN6096
which is the logical place for it to live, but I explored other places
too.
Why would you object to improving the manual?
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-10-05 17:53:03 | Re: Polymorphic arguments and composite types |
| Previous Message | Michael Meskes | 2007-10-05 17:41:44 | Re: Not *quite* there on ecpg fixes |