| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: and it's not a bunny rabbit, either |
| Date: | 2010-12-30 16:00:02 |
| Message-ID: | 1293724725-sup-2027@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Robert Haas's message of jue dic 30 12:47:42 -0300 2010:
> After further thought, I think it makes sense to change this around a
> bit and create a family of functions that can be invoked like this:
>
> void check_relation_for_FEATURE_support(Relation rel);
>
> ...where FEATURE is constraint, trigger, rule, index, etc. The
> function will be defined to throw an error if the relation isn't of a
> type that can support the named feature. The error message will be of
> the form:
>
> constraints can only be used on tables
> triggers can be used only on tables and views
> etc.
So this will create a combinatorial explosion of strings to translate?
I liked the other idea because the number of translatable strings was
kept within reasonable bounds.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-12-30 16:02:04 | Re: Old git repo |
| Previous Message | Tom Lane | 2010-12-30 15:53:24 | Re: Streaming replication as a separate permissions |