| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: PL/Java issues |
| Date: | 2004-01-05 17:49:37 |
| Message-ID: | 200401051849.37706.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
Andrew Dunstan wrote:
> Will we need to address this TODO item:
>
> . Add capability to create and call PROCEDURES
>
> before proceding to do PL/Java? It would add to the usefulness
> greatly, I should think. I'm not sure how hard it would be.
This should be relatively easy if you omit OUT parameters. Just treat
CALL foo(...) as SELECT foo(...) and throw away the result (or avoid
generating one).
For OUT parameters, we'd probably have to learn their full semantics
first.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2004-01-05 17:51:24 | Re: Permissions and PGSQL |
| Previous Message | Ben Clewett | 2004-01-05 17:15:06 | UNSUBSCRIBE |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Barry Lind | 2004-01-05 20:11:47 | Re: SELECT ... FOR UPDATE and ResultSet |
| Previous Message | Thomas Hallgren | 2004-01-05 01:00:37 | Re: [JDBC] PL/Java issues |