X-Original-To: pgsql-interfaces@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id B75634759AF for ; Tue, 18 Feb 2003 20:05:19 -0500 (EST) Received: from news.hub.org (news.hub.org [64.49.215.80]) by postgresql.org (Postfix) with ESMTP id 2BC7747595A for ; Tue, 18 Feb 2003 20:05:19 -0500 (EST) Received: by news.hub.org (Postfix, from userid 8) id 149FB43B3A6; Tue, 18 Feb 2003 20:05:19 -0500 (EST) From: ljb X-Newsgroups: comp.databases.postgresql.interfaces Subject: Re: Announce: A pure-Tcl interface ... PgAccess, Protocol Version Date: Wed, 19 Feb 2003 01:05:19 +0000 (UTC) Organization: Hub.Org Networking Services (http://www.hub.org) Lines: 20 Message-ID: References: X-Complaints-To: usenet@news.hub.org User-Agent: slrn/0.9.7.3 (Linux) To: pgsql-interfaces@postgresql.org X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/76 X-Sequence-Number: 3697 cmaj@freedomcorpse.info wrote: > ... > Maybe I missed it in the docs, but what backend protocols does 1.3.9 > support ? Only the current one, "v2.0", which talks to PostgreSQL-6.4 through at least 7.3.2. (My very first versions talked "v1" to PostgreSQL-6.3.x) I hear a protocol change is coming with PostgreSQL-7.4. I'm hoping there will be a backward-compatible release or two for transition, as there was the last time, and that the protocol won't undergo any extreme radical changes. Of course, this affects the ODBC and JDBC interfaces, too, and they are much larger and presumably harder to update to a new protocol. > Please, let me know on/off list what we can do to at least get PgAccess > running for you. I would be more than happy to help integrate this > patch. I think it's something we can do before we get a "perfect" > release of a cross-platform RAD and DBA toolkit for PostgreSQL. :) OK. Let's continue this on developers at pgaccess.org.