Received: from cook.onecert.fr (cook.onecert.fr [134.212.189.43]) by hub.org (8.8.8/8.7.5) with SMTP id KAA25266 for ; Wed, 12 Aug 1998 10:31:00 -0400 (EDT) Received: (qmail 3463 invoked by uid 501); 12 Aug 1998 14:29:14 -0000 Sender: ecm@cook.onecert.fr To: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] Re: thread-safe libpq and DBD::Pg References: <26919.902847103@sss.pgh.pa.us> <35D0763C.C5D2DBF8@trust.ee> X-Eric-Conspiracy: there is no conspiracy. X-Attribution: ecm X-Home-Page: http://www.chez.com/emarsden/ Reply-To: emarsden@mail.dotcom.fr From: Eric Marsden Date: 12 Aug 1998 16:29:14 +0200 In-Reply-To: Hannu Krosing's message of "Tue, 11 Aug 1998 19:50:04 +0300" Message-ID: Lines: 33 X-Mailer: Gnus v5.6.22/Emacs 19.34 >>>>> "HK" == Hannu Krosing writes: >>>>> "TL" == Tom Lane writes: TL> The present libpgtcl is NOT pure Tcl --- it is a C-coded Tcl TL> extension, besides which it is layered on top of libpq. This is my impression too: in postgresql-6.3.2/src/interfaces/libpgtcl/ there are C files which reference functions like PQconnectdb. However, the documentation for libpgtcl states (this is from the top of postgresql-6.3.2/doc/src/sgml/libpgtcl.sgml) pgtcl is a tcl package for front-end programs to interface with Postgres backends. pgtcl does not use the libpq library but communicates to the backend directly via the frontend-backend protocol. Thus, it is more efficient than previous postgres->tcl bindings which are layered on top of libpq. In addition, pgtcl can handle multiple backend connections from a single frontend application. The documentation looks wrong, or perhaps it is talking about a development version of libpgtcl? Should I report a documentation bug? HK> I've got the impression that there is currently a pure Tcl interface HK> as well that some use with pgAccess on win32. This is ftp://ftp.flex.ro/pub/pgaccess/pgsql.tcl (Tcl interface at the socket level). -- Eric Marsden emarsden @ mail.dotcom.fr It's elephants all the way down