| From: | Richard Harvey Chapman <hchapman(at)3gfp(dot)com> |
|---|---|
| To: | K Parker <kparker(at)eudoramail(dot)com> |
| Cc: | pgsql-general(at)hub(dot)org |
| Subject: | Re: Re: c function |
| Date: | 2000-09-22 21:22:43 |
| Message-ID: | Pine.LNX.4.10.10009221414160.559-100000@smirk.3gfp.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 22 Sep 2000, K Parker wrote:
> > Question: Why isn't 12 printed after the second SELECT statement?
>
> It's the well-known (?) problem that if any function parameter is
> NULL, they are all set to NULL. IIRC someone is working on fixing
> this...
a big thanks to you and Tom for the updates.
a note though: there are no problems with the parameters that I can see.
They're passed correctly to the c function, it's just the return type
that's messed up.
I suppose we'll just have to use 'NULL'.
BTW Is it possible to use a c-function with a prototype like the following
in postgres?
int myfunc (int id, ...);
R.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jie Liang | 2000-09-22 21:41:25 | Re: how to store a query, that results in a table |
| Previous Message | John McKown | 2000-09-22 19:36:34 | Re: one more word about rules (fwd) |