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@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
