Message-ID: <015101c04421$f323e7c0$330a0a0a@6014cwpza006>
From: "Adam Lang" <aalang@rutgersinsurance.com>
To: "Clark, Joel" <jclark@lendingtree.com>
Cc: "pgsql-interfaces" <pgsql-interfaces@postgresql.org>
References: <69F195289743D411B428009027E293C401290EC6@CLTEXCH1>
Subject: Re: Connecting remotely.
Date: Wed, 1 Nov 2000 11:36:56 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

That's sort of what I was thinking... Make a reference to it and use it much
like regobj.dll for modifying Registry in windows...

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Clark, Joel" <jclark@lendingtree.com>
To: "'Adam Lang'" <aalang@rutgersinsurance.com>
Cc: "pgsql-interfaces" <pgsql-interfaces@postgresql.org>
Sent: Wednesday, November 01, 2000 10:35 AM
Subject: RE: [INTERFACES] Connecting remotely.


> Yes, you can build libpq into libpq.dll.  You can then add the function
> declarations at the top, much like you would for an API call.
Alternatively
> you could wrap a COM object around the DLL and use it that way.
>
> Joel
>
> -----Original Message-----
> From: Adam Lang [mailto:aalang@rutgersinsurance.com]
> Sent: Wednesday, November 01, 2000 9:53 AM
> Cc: pgsql-interfaces
> Subject: Re: [INTERFACES] Connecting remotely.
>
>
> That's what I was figuring... so... is it possible to take those files,
> compile them into a dll and make a postgresql-specific remote connection
> library?  So, say instead of referencing ADO in Visual Basic and using the
> ODBC driver, merely wrap up necessary functionality of the client side
> libraries?  Would that be hard? (Never made a DLL before, so unsure).
> Granted it breaks the idea of writing code to use on any database, but if
> you are making an in-house application and have control over the
database...
> Also, it wouldn't help Access oriented people, but this would be used for
a
> bit more hard core integration, something that if you want, you shouldn't
be
> using Access for a front end anyway.
>
> What are people's thoughts?
>
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company
> ----- Original Message -----
> From: "Marko Kreen" <marko@l-t.ee>
> To: "Adam Lang" <aalang@rutgersinsurance.com>
> Cc: "pgsql-interfaces" <pgsql-interfaces@postgresql.org>
> Sent: Wednesday, November 01, 2000 9:50 AM
> Subject: Re: [INTERFACES] Connecting remotely.
>
>
> > On Wed, Nov 01, 2000 at 09:29:47AM -0500, Adam Lang wrote:
> > > This may be a silly question, but how does *nix systems speak to a
> remote
> > > database without ODBC, like Windows?
> >
> > Database's client side libraries take care of that.  But that
> > means linking your app with some particular database library.
> > e.g. PHP has php_pgsql, php_sybase...  if you want your
> > app to be database-agnostic, you can link it with e.g. UnixODBC,
> > which should do the database-specific work.
> >
> > > As an example, PHP... I have Apache/PHP on one server, and the
database
> on
> > > another.  How does it do remote calls?
> >
> > $db = pg_connect("host=another.net port=5432 ... ");
> >
> > --
> > marko