Extracting client code
От | Jon Earle |
---|---|
Тема | Extracting client code |
Дата | |
Msg-id | 4347.142.46.208.244.1159452491.squirrel@kronos.honk.org обсуждение исходный текст |
Ответы |
Re: Extracting client code
|
Список | pgsql-interfaces |
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!
В списке pgsql-interfaces по дате отправления: