From: David Stanaway <david@stanaway.net>
To: pgsql-interfaces@postgresql.org
Subject: Re: Problem with PQexecPrepared
Date: Wed, 09 Jun 2004 17:38:14 -0500
Message-ID: <1086820694.10544.14.camel@dmxnocws13.dialmex.net> (raw)
In-Reply-To: <20040609222114.GI91662@xs4all.nl>
References: <1086817452.10544.5.camel@dmxnocws13.dialmex.net>
<20040609222114.GI91662@xs4all.nl>
On Wed, 2004-06-09 at 17:21, Jeroen T. Vermeulen wrote:
> On Wed, Jun 09, 2004 at 04:44:12PM -0500, David Stanaway wrote:
>
> > The type I am passing is a char** and it is expecting const char*
const*
> Not that it would be a problem here, because the array itself is const
> and so the function could never write its own pointer into it. I
think
> it's one of those rare situations where a cast is justified.
Thanks for the clarification. I thought it was odd to have to cast to a
const in this case. I changed the call like such:
res = PQexecPrepared(serverp->connection,
serverp->queryps[BILLING_INSERTROUTED]->prephandle,
nparm,(const char *const*)parms,NULL,NULL,1);
If the prototype had been for const char** I would not have needed to
change anything, the API author I guess is being thorough.
--
David Stanaway <david@stanaway.net>
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: david@stanaway.net
Subject: Re: Problem with PQexecPrepared
In-Reply-To: <1086820694.10544.14.camel@dmxnocws13.dialmex.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