Re: [HACKERS] Getting the results columns before execution

2004-01-30 Thread Bruce Momjian
Jan Wieck wrote: Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: Tom Lane wrote: Are those exposed through the libpq interface? No, because libpq doesn't really have any concept of prepared statements. It would probably make sense to add some more API to libpq to allow

Re: [HACKERS] Getting the results columns before execution

2004-01-30 Thread Bruce Momjian
Jan Wieck wrote: Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: Tom Lane wrote: Are those exposed through the libpq interface? No, because libpq doesn't really have any concept of prepared statements. It would probably make sense to add some more API to libpq to allow

Re: [HACKERS] Getting the results columns before execution

2004-01-29 Thread Jan Wieck
Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: Tom Lane wrote: Are those exposed through the libpq interface? No, because libpq doesn't really have any concept of prepared statements. It would probably make sense to add some more API to libpq to allow creation and interrogation of

Re: [HACKERS] Getting the results columns before execution

2004-01-25 Thread Tom Lane
Bruce Momjian [EMAIL PROTECTED] writes: Tom Lane wrote: Are those exposed through the libpq interface? No, because libpq doesn't really have any concept of prepared statements. It would probably make sense to add some more API to libpq to allow creation and interrogation of prepared

Re: [HACKERS] Getting the results columns before execution

2004-01-24 Thread Bruce Momjian
Tom Lane wrote: Shachar Shemesh [EMAIL PROTECTED] writes: Tom Lane wrote: Sure it is, if you are using the V3 protocol (new in 7.4). See the Describe message types. Are those exposed through the libpq interface? No, because libpq doesn't really have any concept of prepared

[HACKERS] Getting the results columns before execution

2004-01-19 Thread Shachar Shemesh
Hi all, From the OLE DB manual: The consumer can also get information about the columns of the rowset by calling IColumnsInfo::GetColumnInfo, which all providers must support, or IColumnsRowset::GetColumnsRowset, which providers may support, on the command. Before calling GetColumnInfo or

Re: [HACKERS] Getting the results columns before execution

2004-01-19 Thread Darko Prenosil
On Monday 19 January 2004 15:13, Shachar Shemesh wrote: Hi all, From the OLE DB manual: The consumer can also get information about the columns of the rowset by calling IColumnsInfo::GetColumnInfo, which all providers must support, or IColumnsRowset::GetColumnsRowset, which providers may

Re: [HACKERS] Getting the results columns before execution

2004-01-19 Thread Tom Lane
Shachar Shemesh [EMAIL PROTECTED] writes: ... This is a problem, as merely preparing a command is not enough to get the returned rows information. Sure it is, if you are using the V3 protocol (new in 7.4). See the Describe message types. regards, tom lane

Re: [HACKERS] Getting the results columns before execution

2004-01-19 Thread Shachar Shemesh
Tom Lane wrote: Shachar Shemesh [EMAIL PROTECTED] writes: ... This is a problem, as merely preparing a command is not enough to get the returned rows information. Sure it is, if you are using the V3 protocol (new in 7.4). See the Describe message types. regards, tom lane Are those

Re: [HACKERS] Getting the results columns before execution

2004-01-19 Thread Tom Lane
Shachar Shemesh [EMAIL PROTECTED] writes: Tom Lane wrote: Sure it is, if you are using the V3 protocol (new in 7.4). See the Describe message types. Are those exposed through the libpq interface? No, because libpq doesn't really have any concept of prepared statements. It would probably make