From: Jon Earle <jepg@kronos.honk.org>
To: pgsql-interfaces@postgresql.org
Subject: Extracting client code
Date: Thu, 28 Sep 2006 10:08:11 -0400 (EDT)
Message-ID: <4347.142.46.208.244.1159452491.squirrel@kronos.honk.org> (raw)
Hi folks,
I have a need to extract the postgres client code from the tarball for
inclusion into a separate application. This app will talk to a PG database
(obviously) over a network and will be the only app that will be
communicating with the database (aside from a PHP application on the same box
as the PG server). This app will be compiled on various platforms - AIX,
HPUX, Solaris, Linux and Unixware are the main ones that come to mind. I
have no specific need to keep the PG code in a library so compiling the PG
client code together with my application code module is not only acceptable,
it would be preferred.
Currently, the app is using mysql client code in this precise fashion - I'd
like to "simply" replace the mysql code with postgres code for our own
consistency.
Before I get too far into working this up, at this point, I'm really just
curious if this is doable. Can I just take the src/interface/libpq dir
contents, parachute them into the same dir as my app, then just compile it
all together (after making the appropriate changes to my own app, of course)?
Thanks for any insight!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: jepg@kronos.honk.org
Subject: Re: Extracting client code
In-Reply-To: <4347.142.46.208.244.1159452491.squirrel@kronos.honk.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox