| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Don Y <pgsql(at)DakotaCom(dot)Net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: ISSTRICT behavior |
| Date: | 2006-05-04 06:34:27 |
| Message-ID: | 20060504063427.GA4752@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Don Y | 2006-05-04 06:43:07 | Re: ISSTRICT behavior |
| Previous Message | carlosreimer | 2006-05-04 06:29:41 | RES: pg_dumpall error |