From: | Markus Schaber <schabios(at)logi-track(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: [JDBC] Where are we on stored procedures? |
Date: | 2005-02-25 18:08:45 |
Message-ID: | 421F69AD.1000803@logi-track.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
Hi, Francisco,
Francisco Figueiredo Jr. schrieb:
> In fact, I think people keep requesting me support on Npgsql for that
> because MS Sql server supports it and they are porting their code to use
> Postgresql and facing that difficult.
>
> Indeed, for (a) we could use an approach similar to Ms sql server. We
> could have a way of the procedure say if it wanted to send the rows
> affected information or not.
> And about (b) I think that it is only on trivial cases that people
> really want to use this feature :)
As you need to tweak the function/procedure source to implement (a), you
can also tweak the function/procedure to return the row cound and
whatever other diagnostics you need.
For newly implemented stored procedures, we could create a special
diagnostics result set that every procedure creates. This usually
contains some success/error information, but the procedure could add
additional rows to it.
Markus
--
markus schaber | dipl. informatiker
logi-track ag | rennweg 14-16 | ch 8001 zürich
phone +41-43-888 62 52 | fax +41-43-888 62 53
mailto:schabios(at)logi-track(dot)com | www.logi-track.com
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2005-02-25 18:10:50 | Re: Development schedule |
Previous Message | Peter Eisentraut | 2005-02-25 18:05:18 | Re: [pgsql-hackers] Daily digest v1.4988 (21 messages) |
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Schaber | 2005-02-25 18:21:02 | Re: [JDBC] Where are we on stored procedures? |
Previous Message | Dave Smith | 2005-02-25 16:21:10 | Re: setFetchSize question |