Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: C-Interface Amound of Tupels in Result after COPYout
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: bert(dot)horvath(at)fh-erfurt(dot)de
- Cc: pgsql-interfaces(at)postgresql(dot)org
- Subject: Re: C-Interface Amound of Tupels in Result after COPYout
- Date: Thu, 15 Nov 2007 10:27:00 -0500
- Message-id: <2564.1195140420@sss.pgh.pa.us> <text/plain>
Bert Horvath <bert(dot)horvath(at)fh-erfurt(dot)de> writes: > do i have any chance to get the amount of tupels in the result set after > executing a query with a copy command? Its not a problem to count the > columns with PQnFields(*conn,*result) but there is no documentation für > PQnTupels(*conn,*result) and it does not work. PQcmdTuples. PQnTuples is for the number of rows actually returned to the client by a SELECT. regards, tom lane
- Follow-Ups:
- Re: C-Interface Amound of Tupels in Result after COPYout
- From: Bert Horvath
- Re: C-Interface Amound of Tupels in Result after COPYout
- References:
- C-Interface Amound of Tupels in Result after COPYout
- From: Bert Horvath
- C-Interface Amound of Tupels in Result after COPYout
- Prev by Date: C-Interface Amound of Tupels in Result after COPYout
- Next by Date: Re: C-Interface Amound of Tupels in Result after COPYout
- Previous by thread: C-Interface Amound of Tupels in Result after COPYout
- Next by thread: Re: C-Interface Amound of Tupels in Result after COPYout
- Indexes: