Received: from flex.flex.ro (flex.flex.ro [193.230.255.2]) by hub.org (8.8.8/8.7.5) with ESMTP id HAA15632 for ; Tue, 13 Jan 1998 07:46:19 -0500 (EST) Received: from flex.flex.ro (localhost [127.0.0.1]) by flex.flex.ro (8.8.8/8.7.3) with SMTP id OAA09622; Tue, 13 Jan 1998 14:44:09 +0200 Sender: teo@flex.flex.ro Message-ID: <34BB6199.2155538B@flex.ro> Date: Tue, 13 Jan 1998 14:44:09 +0200 From: Constantin Teodorescu Organization: FLEX Consulting Braila X-Mailer: Mozilla 3.04Gold (X11; I; Linux 2.0.32 i586) MIME-Version: 1.0 To: Herouth Maoz CC: PostgreSQL Interfaces Subject: Re: [INTERFACES] Re: [QUESTIONS] Connect to Postgres with pure TCL References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Herouth Maoz wrote: > > However, your way would be much more logical, though I suspect a > performance degredation if all the connections are done in the interpreted > language itself. I don't think so. SQL conversation mean some small messages for establishing protocol then sending the SQL command and after that receiving data. The most part of the time is taken by data transferring over the network. I would bet on a maximum 5% performance degrading. Tcl/Tk 8.0 would be the only version that could deal with binary i/o over files and sockets. In my opinion, it wouldn't be so hard to rewrite pg interface directly in Tcl. I would study that posibility and keep you informed. -- Constantin Teodorescu FLEX Consulting Braila, ROMANIA