Darko Prenosil wrote:
> It is wrapper about libpq client library functions for use in PL/PSQL.
> I agreed with Joe Conway that it may fit within dblink, because dblink is much
> more easy to work with than the libpq, but sometimes it is Just not enough.
> So, the idea is to re-implement all i
It is wrapper about libpq client library functions for use in PL/PSQL.
I agreed with Joe Conway that it may fit within dblink, because dblink is much
more easy to work with than the libpq, but sometimes it is Just not enough.
So, the idea is to re-implement all important libpq functions lik
Would you tell us exactly what this is.
---
Darko Prenosil wrote:
> Tree weeks later than I promised, but it is finished (I hope).
>
> In attachment are files:
> dblink.c
> dblink.h
> dblink.sql.in
>
Tree weeks later than I promised, but it is finished (I hope).
In attachment are files:
dblink.c
dblink.h
dblink.sql.in
pqtest.sql
In file pqtest.sql is sample queries and results. It seem OK to me.
There are two reasons why I did not make a diff.
1. The
I come to an idea using dblink from a contrib
directory:
Why my pl/psql function can't use common PQ stuff
to connect to other database ?
So I wrote a wrapper around PQ functions and
registered them in postgres.
Now I can write pl/psql functions
like:
CREATE OR REPLACE FUNCTION TestPQ
(
