"Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)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
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
pgsql-interfaces by date
|Next:||From: Hiroki Kataoka||Date: 1998-12-16 12:27:47|
|Subject: RE: [INTERFACES] The problem between libpq and libpgtcl for WIN32|
|Previous:||From: Byron Nikolaidis||Date: 1998-12-14 20:17:49|
|Subject: Re: [INTERFACES] bug in ODBC driver ?|