Re: ISSTRICT behavior

Martijn van Oosterhout wrote:
> On Wed, May 03, 2006 at 11:02:26PM -0700, Don Y wrote:
>> (sigh)  Sorry to be picking nits.  I'm just trying to
>> sort out how to protect against folks making careless
>> mistakes in the future (e.g., forgetting STRICT in
>> the function declarations when adding a function to
>> a database, etc)
>
> Unfortunatly there is no way to ensure the user declares the function
> in SQL in the way your code expects. I remember a discussion once about
> allowing you to declare the essential function details in the C file so
> that Postgres could complain if the user got it wrong, but nothing ever
> came of it.
>
> In short, give them an INSTALL.sql and tell them to use it.

Is there any way to prevent them from *adding* these functions
(i.e. build them into template) so they have to use them the
way *I* have already defined them?