| From: | Don Y <pgsql(at)DakotaCom(dot)Net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org, kleptog(at)svana(dot)org |
| Subject: | Re: ISSTRICT behavior |
| Date: | 2006-05-04 06:45:31 |
| Message-ID: | 4459A30B.1030206@DakotaCom.Net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-05-04 06:48:02 | Re: ISSTRICT behavior |
| Previous Message | Don Y | 2006-05-04 06:43:07 | Re: ISSTRICT behavior |