Subject | Re: Anyone know what this error means, isc_req_sync? |
---|---|
Author | kshenes |
Post date | 2004-07-27T14:12:01Z |
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:
encountering this error when retrying an a select statement after
encountering a limbo transaction error. So does this mean the
transaction is out of limbo state and the query has proceeded before
I retry? What is the best way to handle limbo transactions errors
encountered during a query?
Thanks
Kevin
wrote:
> At 10:55 PM 26/07/2004 +0000, you wrote:cannot
> >I am getting th error "isc_req_sync" a lot all of a sudden. I
> >find any mention of this in the Docs (at least the ones I knowabout).
> >or any mention of it on the internet. Can someone fill me in onhow to
> >avoid this error condition, and what it means.From hazy
>
> It is gdscode 335544364 req_sync Request synchronization error.
> recollection, it occurs when the application requests a requery fora
> select statement while the statement is still fetching or callsrollback or
> commit on a transaction that has requests in this state.loop that
>
> If so (no guarantees!!) then you could put the request in a retry
> catches this exception. If the queries are outside your control,e.g. a
> user can request a SELECT * on a table with 5 million rows, youshould
> probably limit the number of retries before denying the requestThis is very helpful, Thanks. Now an addition tidbit. I am
> absolutely. There isn't currently a way to stop a runaway query.
>
>
> >I am running v1.0.3 on debian linux.
>
> Pleased to hear it!
>
> /heLen
encountering this error when retrying an a select statement after
encountering a limbo transaction error. So does this mean the
transaction is out of limbo state and the query has proceeded before
I retry? What is the best way to handle limbo transactions errors
encountered during a query?
Thanks
Kevin