From: Ken J. Wright <ken@ori-ind.com>
To: Kovacs Zoltan Sandor <tip@pc10.radnoti-szeged.sulinet.hu>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Function sequence error with ODBCExpress
Date: Tue, 01 Aug 2000 16:57:16 -0700
Message-ID: <3.0.1.32.20000801165716.00a44c10@ori-ind.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10008020153080.22136-100000@pc10.radnoti-sze ged.sulinet.hu>
References: <Pine.LNX.4.05.10008012138490.21449-100000@pc10.radnoti-szeged.sulinet.hu>
At 01:57 08/02/2000 +0200, Kovacs Zoltan Sandor wrote:
>> Commiting or Aborting the inserted rows will work fine, whether you're
inserting
>> the rows positionally or using an INSERT SQL statement, however after
you commit
>> or abort (or probably before you commit or abort) you must close the result
>> sets, since the ODBC driver you're using will cause the result set
cursors to be
>> closed on the commit or abort (and tehreby causing function sequence
errors when
>> you try to access the result sets afterwards). Afterwards you can open the
>> result sets again.
>>
>> ------------------------------------------------------------------------
>>
>> End of quoting. Is the solution what the answers suggest? It would be
>> great if the result sets need not to be closed. What is your solution for
>> this?
>
>The things above seem to be true: each dataset should be closed and then
>all must be reopen which is linked to a grid. Now there is no "Function
>sequence error" for us, but it is painful to close them datasets all the
>time... :-(
I can't remember the odbc driver insides well enough, but I'll check
tomorrow. Maybe Byron is listening? Anyway, I use ODBCExpress with Delphi
in both forms and grids without trouble. But I don't use COMMITs or ABORTs
directly. The OE api handles all the low end stuff quite well when using
grids and such. I'll use exception handling when executing hstmt sql
statements. I only need to close/reopen datasets when keeping detail
datasets current with their master. OE is (was?) sometimes not reliable
with automatic master/detail grids. But I've never had to close/reopen with
each insert/update/delete in a dataset.
Ken
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: ken@ori-ind.com, tip@pc10.radnoti-szeged.sulinet.hu
Subject: Re: Function sequence error with ODBCExpress
In-Reply-To: <3.0.1.32.20000801165716.00a44c10@ori-ind.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox