Skip site navigation (1) Skip section navigation (2)


From: Byron Nikolaidis <byron(dot)nikolaidis(at)home(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Stephen Martin Trans-Euro I(dot)T Ltd" <stephen(at)sealteam(dot)demon(dot)co(dot)uk>, pg-interfaces <pgsql-interfaces(at)hub(dot)org>
Subject: Re: [INTERFACES] More VB
Date: 1999-07-25 02:10:28
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces

Tom Lane wrote:
> "Stephen Martin Trans-Euro I.T Ltd" <stephen(at)sealteam(dot)demon(dot)co(dot)uk> writes:
> > whilst it seems driving libpq.dll from VB might be a difficult
> > enterprise..  is it still not possible to just connect a socket to
> > port 5432 of where ever and start communicating with postgres through
> > a socket?  TCP or UDP?
> Sure, if you can cope with binary-oriented data structures being
> returned to you by the server.  (The actual data is text, as long as you

I think I missed part of the conversation, but my take on it is that if
you already have a "libpq.dll", it should be fairly straightforward to
map the functions of the dll to VB, just as long as the dll follows
certain rules in how it exports the functions.   I have created dll's
before, and mapped the functions to VB quite successfully.  The only
thing to worry about on the VB side is to correctly map the 'C' function
arguments and return values to VB data types.


In response to

pgsql-interfaces by date

Next:From: eem21Date: 1999-07-25 19:32:56
Subject: libpq - PQsetenv and its new sister functions
Previous:From: The Hermit HackerDate: 1999-07-24 17:11:03
Subject: Re: [HACKERS] Re: SSL patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group