Thread: WIN-client wanted ...

I'm in need for a thin libpq library under Win'32.

There has been a libpq-library available on the net with just the
libpq-dll and this worked very well with my application (written
with Borland CBuilder 4).

Some days ago a new compilation has been put on the net (6.5.3)
and I can not use it because it always gives me segamentation
faults - we were unable to use any library, which was build
using the cygnus development kit :-(

Some help out there ?



Marten Feldtmann

Marten Feldtmann wrote:

> I'm in need for a thin libpq library under Win'32.

it is amazing how few people seem to be using libpq.dll! my next project
will need some kind of client server db access and I'm seriously
considering using libpq.dll; I won't need a full blown SQL engine, just
a way to store and retrieve records with row-level locking and
transaction support;

is libpq.dll as under-used as I deduce from reading this list?

beers,

--
Otavio Exel /<\oo/>\ oexel@economatica.com.br

> Marten Feldtmann wrote:
>
> > I'm in need for a thin libpq library under Win'32.
>
> it is amazing how few people seem to be using libpq.dll! my next project
> will need some kind of client server db access and I'm seriously
> considering using libpq.dll; I won't need a full blown SQL engine, just
> a way to store and retrieve records with row-level locking and
> transaction support;
>
> is libpq.dll as under-used as I deduce from reading this list?
>

 Hmmm, libpq without a full blown SQL engine somewhere does not make sense -
therefore I do not understand your question above - libpq just give you the
communication to this full blown sql engine.

 It seems to be dependent of the platform one is using. On Windows'xyz you
use ODBC in nearly all the places. But I've also heard, that some projects
do not use ODBC und just use the low-level libraries from Oracle or IBM to
get rid of the additional odbc structure. When it comes to products suitable
for several databases it may be useful to use odbc.

 I myself just would like to have the thin libpq.dll and libpq.lib for the
case NOT to use the ODBC structure of Windows and therefore make everyone the
connectivity to our database product available.

 Another point is the thin structure of the API of PostgreSQL. There has
been a libpq available for PostgreSQL 6.4.2 on the net ... but with 6.5.x
I've seen nothing like this. I had thought, that the odbc dll would had
the libpq also, but it seems, that they integrate the libpq stuff into
the odbc library.

 Marten