Jong, I did not make much changes to the fpc files itself. The only change I
made to the api wrapper is the location of the libpq.so / dll file. It use
to load from current working dir, or going on a rampant search according to
the LD_LIBRARY_PATH environment variable on linux. I made a mod where t
Desmond Coertzen wrote:
I tried TPQConnection in a production environment on a server-side
deamon, and bytea was the first missing data type that haunted me. The
"encode" postgres function will save you here: Encode your bytea field
I can't remember, but I think bytea (I call it blob) work fi
Hi Graeme,
The libpq_api.pas that ships with FPC implements all the functions from the
version 3 native api on windows and linux. This .so/.dll is backwards
compatible even with the latest versions of postgresql server.
I tried TPQConnection in a production environment on a server-side deamon,
an
2009/8/16 Joost van der Sluis :
> But it's this way because nobody looked at it before, and all those
> things like column_datatype are effectively used by no-body, afaik. But
> patches are welcome. (The only reason this function is implemented at
> all is that it is used by Connection.getTableName
Op zaterdag 08-08-2009 om 19:03 uur [tijdzone +0200], schreef Graeme
Geldenhuys:
> 1..)
> In the function TPQConnection.GetSchemaInfoSQL(..) there is the following SQL
> statements.
> * First off, this statement doesn't return a single row when I run it
> directly in psql or pgAdmin III.
> * Wh
Hi,
I have recently been playing around with PostgreSQL and SqlDB. I seem to have
quite a few problems. tiOPF's test suite normally gives database components a
good workout and currently SqlDB + PostgreSQL has about 40 tests failing out of
160 tests. SqlDB + Firebird does much better, but stil
