This is pgin.tcl/README.PGAccess, describing using PGAccess with pgin.tcl
Last updated for pgin.tcl-1.3.9 on 2003-02-13
-----------------------------------------------------------------------------

DOES pgin.tcl WORK WITH PGACCESS?

The idea is to use pgin.tcl and avoid having system-specific DLLs or
shared libraries for libpgtcl and libpq.

With patches to PGAccess, it could work. But PGAccess doesn't seem to work
at all for me, so I have been unable to create the patches.  Neither the
so-called "stable" release pgaccess-0.98.8, nor the current snapshot
pgaccess-0.98.8.20030117, seem stable enough for me to try to create a patch
for pgin.tcl.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

There are three known issues with PGAccess and pgin.tcl:

(1) Loading - PGAccess will need to be patched to not try to load the
shared libpgtcl object, but source pgin.tcl instead. This is easy.

(2) Connecting - Since pgin.tcl does not support the old-style pg_connect
form, nor Unix Domain Sockets, it will be necessary to make sure PGAccess
uses the new-form connect command and always uses TCP/IP sockets. This
seems to work as long as you specify a username in the PGAccess connect
dialog. (If you leave the hostname blank, libpgtcl will use UDS but
pgin.tcl will use TCP/IP to "localhost".) So this is also easy.

(3) Import/Export - Newer versions of PGAccess use front-end COPY like psql
"\copy". (Older versions used back-end copy, which will never work with any
secure installation.) The latest pgin.tcl does support COPY but is not 100%
compatible with libpgtcl. It isn't hard to write code which will do COPY
with either libpgtcl or pgin.tcl transparently (see REFERENCE), but the PGAccess
Import/Export code is unusual so this may not be as easy.
