Received: from mail.rdc1.md.home.com (imail@ha1.rdc1.md.home.com [24.2.2.66]) by hub.org (8.10.1/8.10.1) with ESMTP id e57LXMc78713 for ; Wed, 7 Jun 2000 17:33:22 -0400 (EDT) Received: from byron ([24.4.141.52]) by mail.rdc1.md.home.com (InterMail vM.4.01.02.00 201-229-116) with SMTP id <20000607213310.DHJU23916.mail.rdc1.md.home.com@byron>; Wed, 7 Jun 2000 14:33:10 -0700 Message-ID: <001501bfd0c7$a3107fa0$6401a8c0@byron> From: "Byron Nikolaidis" To: "Mihai Gheorghiu" , References: <000801bfd08e$54606480$c39c103f@new6> Subject: Re: Win ODBC drivers for Postgres Date: Wed, 7 Jun 2000 17:30:43 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 X-Archive-Number: 200006/47 Hey there partner, To quote the immortal Butthead: "uhhhh....................., ok." Seriously, I wonder how this "consultant" came up with this? Sounds awefully generalized. I think I could say that line about anything, including ODBC itself. Also, many of the compromises of the ODBC driver are based on shortcomings of the backend. Jeez, we still "simulate" a Prepared Statement because there isn't one in the backend. Is the backend ever gonna have this?AFAIK, the JDBC driver simulates the prepared statement also. Some may remember the "declare/fetch" feature of the ODBC driver, that makes use of postgres cursors. This feature was added to help with the network bandwidth problem -- instead of getting the entire query result, it fetched it in chunks when required. Yeah, so maybe connection pooling would be nice, but most things use one or two connections don't they? Do most processes keep asking odbc for a new connection? Byron ----- Original Message ----- From: Mihai Gheorghiu To: Sent: Wednesday, June 07, 2000 10:36 AM Subject: [INTERFACES] Win ODBC drivers for Postgres > The following is a quote from a consultant's opinion on my intention to > migrate to Postgresql. > Quote: > [ODBC public domain drivers] are immature, inefficient and are network > bandwidth hogs. The public domain drivers don't support connection caching > which reuses an existing database connection for same queries to reduce the > query result time. > Unquote. > Please comment. > > Best regards, > > Mihai > > PS See also pgsql-general for opinion on Postgres :-) >