Re: libpq Describe Extension [WAS: Bytea and perl] - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: libpq Describe Extension [WAS: Bytea and perl]
Date
Msg-id effcd16427ace40d33f83e8e53dcb40e@biglumber.com
Whole thread Raw
In response to Re: libpq Describe Extension [WAS: Bytea and perl]  (Volkan YAZICI <yazicivo@ttnet.net.tr>)
Responses Re: libpq Describe Extension [WAS: Bytea and perl]
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> think it would be quite handy to be able to gather information
> about a prepared stmt in later phases of an application. For
> instance one might need to get the parameter and row types of
> a prepared query that he/she isn't created.

Prepared statements are not visible nor survivable outside of your
session, so this doesn't really make sense. If your application needs
the information, it can get it at prepare time.

>> Anyone have a need to get the result type info during PQprepare?

> I don't think so. And if one would ever need such an information, can
> reach it quite easily via PQdescribePrepared().

That's a good point, however, along with your other arguments. :) I
could live with either way.

- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200608110849
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFE3Hz8vJuQZxSWSsgRAuJuAJ4z/LmnoLOXIoZcdSh0VFYCdBDMlwCfd3HW
8YOwN30Jb8jHGx/OOjWzPaQ=
=9tRi
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Difference Between record and rowtype
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Bison Version