Received: from gauss.deltav.hu (gauss.deltav.hu [194.9.64.225])
	by hub.org (8.9.3/8.9.3) with ESMTP id PAA31623
	for <pgsql-interfaces@postgresql.org>;
	Tue, 4 Apr 2000 15:58:09 -0400 (EDT)
	(envelope-from tip@pc10.radnoti-szeged.sulinet.hu)
Received: from tir (97.dial02.deltav.hu [194.9.64.97]) by gauss.deltav.hu
	(Netscape Messaging Server 3.6)  with SMTP id AAB138F;
	Tue, 4 Apr 2000 21:58:26 +0200
From: Zoltan Kovacs <tip@pc10.radnoti-szeged.sulinet.hu>
To: Byron Nikolaidis <byron.nikolaidis@home.com>
Subject: Re: ODBC: SELECT COMMITs a TRANSACTION
Date: Tue, 4 Apr 2000 21:06:45 +0200
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
Cc: pgsql-interfaces@postgresql.org
MIME-Version: 1.0
Message-Id: <00040422073301.15602@tir>
Content-Transfer-Encoding: 8bit
X-Archive-Number: 200004/21

Dear Byron,

thank you for your instructions. We tried the ODBC driver without the 'fetch'
option, it works well. Unfortunately this implies that the BDE loads all the
selected table down. The result will be a rather slow query if we want to show the full
table in a grid, especially selecting large tables.

In our opinion a transaction should not be closed when the user sends a SELECT
statement. Are there other database engines which demand this feature? If not,
it should be called as a bug and put it onto the TODO list and talk about it in
the documentation.

We are in a need of handling this on tables containing many rows (~1000). If you
could please help, that where we can start to work, we may try to modify the
sources. I'm not sure we are able to do this, but maybe.

Thanks in advance.

Regards,
Zoltan