Received: from cltexch1.lendingtree.net (cltexch1.lendingtree.net [207.238.49.106]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eA1FZpl65567 for ; Wed, 1 Nov 2000 10:35:51 -0500 (EST) (envelope-from jclark@lendingtree.com) Received: by CLTEXCH1 with Internet Mail Service (5.5.2650.21) id ; Wed, 1 Nov 2000 10:35:33 -0500 Message-ID: <69F195289743D411B428009027E293C401290EC6@CLTEXCH1> From: "Clark, Joel" To: "'Adam Lang'" Cc: pgsql-interfaces Subject: RE: Connecting remotely. Date: Wed, 1 Nov 2000 10:35:30 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Archive-Number: 200011/8 X-Sequence-Number: 41 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" To: "Adam Lang" Cc: "pgsql-interfaces" 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