pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomasz Myrta <jasiek@klaster.net>
To: creid <creid@netbcg.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: LIBPQ Question
Date: Mon, 27 Oct 2003 08:15:40 +0100
Message-ID: <3F9CC61C.8010103@klaster.net> (raw)
In-Reply-To: <ILECJKPFOLBAGINIFFFBMECECAAA.creid@netbcg.com>
References: <ILECJKPFOLBAGINIFFFBMECECAAA.creid@netbcg.com>

Dnia 2003-10-27 00:08, Użytkownik creid napisał:

> Problem:  Assigning a COUNT(*) result into an integer variable in my C
> program consistently fails except when I assign the same result to a char
> variable.  I can only assume that the internal data type the COUNT function
> uses is integer.
> 
> Can anyone help put me in the proper mindset so I may deal with this,
> seemingly simple issue, to resolution.
> 
> I need the integer result to to help me satisfy a dynamic memory
> requirement... COUNT(*) result will tell me how many rows of data I need to
> malloc and I cannot perform a math operation on a char variable.

All libpq results are strings.
some_int_value=atoi(PQgetvalue(...))

Anyway why do you need count(*) ? When you retrieve your rows, you can 
always check how many are them using PQntuples(...) and then malloc your 
memory tables.

Regards,
Tomasz Myrta




view thread (7+ messages)  latest in thread

Message-ID: <3F9CC61C.8010103@klaster.net>
Permalink:  ../3F9CC61C.8010103@klaster.net/
Also on:    postgresql.org/message-id/3F9CC61C.8010103@klaster.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: jasiek@klaster.net, creid@netbcg.com
  Subject: Re: LIBPQ Question
  In-Reply-To: <3F9CC61C.8010103@klaster.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox