| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: Typed table DDL loose ends |
| Date: | 2011-04-18 14:48:19 |
| Message-ID: | 20110418144819.GA19494@tornado.leadboat.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 18, 2011 at 10:20:21AM -0400, Robert Haas wrote:
> I tweaked the comments accordingly, and also reverted your change to
> the error message, because I don't want to introduce new terminology
> here that we're not using anywhere else.
FWIW, the term "stand-alone composite type" appears twice in our documentation.
> I also thought about making this use parserOpenTable() rather than
> relation_open(), but it turns out that's not so easy, because the
> typed table name is getting shoved into a TypeName rather than a
> RangeVar. I don't think that's the choice I would have made but I'm
> not sure how excited it's worth getting about it.
I hadn't thought about this angle.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-04-18 14:57:07 | Re: JDBC connections to 9.1 |
| Previous Message | Tom Lane | 2011-04-18 14:41:07 | Re: Open issues for collations |