| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ALTER TYPE 2: skip already-provable no-work rewrites |
| Date: | 2011-02-07 01:18:32 |
| Message-ID: | 20110207011832.GA20381@tornado.gateway.2wire.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Feb 06, 2011 at 12:54:19PM -0500, Robert Haas wrote:
> On Sun, Feb 6, 2011 at 12:13 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > That's not quite so good for translators, I think.
> >
> > Another option is that we could just say "relation" (table, foreign
> > table, etc...) or "type". ?We use the word relation as a more generic
> > version of table in a few other places.
Seems fine.
> Or how about passing an ObjectType? Then we could specify
> OBJECT_TABLE, OBJECT_FOREIGN_TABLE, or OBJECT_TYPE.
Could this be done without a several-line blob of code at each call site to
determine the answer? If and only if so, this sounds better.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Hunsaker | 2011-02-07 02:13:22 | Re: [COMMITTERS] pgsql: Force strings passed to and from plperl to be in UTF8 encoding. |
| Previous Message | Andrew Dunstan | 2011-02-07 01:02:05 | Re: [COMMITTERS] pgsql: Force strings passed to and from plperl to be in UTF8 encoding. |