Postgres Pro
Downloads
Home   >   mailing lists

Thread: More VB

More VB

From
"Stephen Martin Trans-Euro I.T Ltd"
Date:
Hello,
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?

Just like simple email clients connect to port 110 of a server and send

user fred
pass mypass

list

RETR 1

etc ...

any thoughts on this?

Stephen

Re: [INTERFACES] More VB

From
Tom Lane
Date:
"Stephen Martin Trans-Euro I.T Ltd" <stephen@sealteam.demon.co.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
don't use BINARY CURSORs, but it's wrapped in header and count fields
that are not.)  libpq isn't doing anything that's particularly magic.
See the "Frontend/Backend Protocol" chapter of the Developer's Guide for
all the gory details of the client-to-server protocol.
        regards, tom lane

Re: [INTERFACES] More VB

From
Byron Nikolaidis
Date:

Tom Lane wrote:
> 
> "Stephen Martin Trans-Euro I.T Ltd" <stephen@sealteam.demon.co.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.

Byron