From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hiroshi Inoue <Inoue@tpf.co.jp>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] The problem between libpq and libpgtcl for WIN32
Date: Mon, 14 Dec 1998 20:25:03 -0500
Message-ID: <12466.913685103@sss.pgh.pa.us> (raw)
In-Reply-To: <000101be274a$3de91060$2801007e@cadzone.tpf.co.jp>
"Hiroshi Inoue" <Inoue@tpf.co.jp> writes:
> The treatment of pgresStatus[] in libpq must be changed ?
> In case of Windows,global data interface between dll's is
> different from UNIX.
> If fact,libpgtcl references global data pgresStatus[] in libpq
> and pg_result -status command does not work properly for
> Windows.
I don't think we can really take pgresStatus[] out of libpq's API,
since that would break existing applications for no good reason.
But it seems reasonable to add a corresponding function call, say
const char * PQresStatus (ExecStatusType status);
and change libpgtcl to use that instead. We could even deprecate
use of the global array with an eye to removing it someday ...
not very soon though.
Anyone have an objection, or a different opinion about what the function
should be named?
regards, tom lane
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: tgl@sss.pgh.pa.us, Inoue@tpf.co.jp
Subject: Re: [INTERFACES] The problem between libpq and libpgtcl for WIN32
In-Reply-To: <12466.913685103@sss.pgh.pa.us>
* 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