X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id D8FC8563CB;
	Fri, 25 Feb 2005 18:08:27 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 69900-07; Fri, 25 Feb 2005 18:08:25 +0000 (GMT)
Received: from mail.logi-track.com (burro.logi-track.com [213.239.193.212])
	by svr1.postgresql.org (Postfix) with ESMTP id 3A2F9563BE;
	Fri, 25 Feb 2005 18:08:24 +0000 (GMT)
Received: from kingfisher.intern.logi-track.com (pD95DCE36.dip0.t-ipconnect.de
	[217.93.206.54])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.logi-track.com (Postfix) with ESMTP id 405B4308D6;
	Fri, 25 Feb 2005 19:08:50 +0100 (CET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by kingfisher.intern.logi-track.com (Postfix) with ESMTP id BE95CAB0E1;
	Fri, 25 Feb 2005 19:08:45 +0100 (CET)
Message-ID: <421F69AD.1000803@logi-track.com>
Date: Fri, 25 Feb 2005 19:08:45 +0100
From: Markus Schaber <schabios@logi-track.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20050116)
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: pgsql-hackers@postgresql.org
Cc: pgsql-jdbc@postgresql.org
Subject: Re: [JDBC] Where are we on stored procedures?
References: <20050224214935.57272.qmail@web60703.mail.yahoo.com>
	<28071.1109284368@sss.pgh.pa.us> <421F39E0.9000706@yahoo.com.br>
In-Reply-To: <421F39E0.9000706@yahoo.com.br>
X-Enigmail-Version: 0.90.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/signed; micalg=pgp-ripemd160;
	protocol="application/pgp-signature";
	boundary="------------enig6F409D308C75C91C259C0D9C"
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO
X-Spam-Level: 
X-Archive-Number: 200502/942
X-Sequence-Number: 64770

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig6F409D308C75C91C259C0D9C
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 us=
e
> Postgresql and facing that difficult.
>=20
> 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

--=20
markus schaber | dipl. informatiker
logi-track ag | rennweg 14-16 | ch 8001 z=FCrich
phone +41-43-888 62 52 | fax +41-43-888 62 53
mailto:schabios@logi-track.com | www.logi-track.com


--------------enig6F409D308C75C91C259C0D9C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCH2mtOVWsnapT9i0RAzQQAJ9ykX30idjwezlmcTIt01EieL/qtQCgieWo
kx4j1B0wLSQbcP2JRbBHFXc=
=Y6+K
-----END PGP SIGNATURE-----

--------------enig6F409D308C75C91C259C0D9C--