Subject | IBO4: LOCATE / UPDATE problem |
---|---|
Author | Tobias Giesen |
Post date | 2001-07-07T21:16:59Z |
Hi!
I have a regular SELECT * type of query without even a WHERE. I do a couple
of Locates:
Locate('ID',idnum,[]).
I then do Edit, modify a field, and Post, and on with the next Locate.
Most of the Locates work. But right in the middle of 20 or so working
Locate's, one of them fails even though the ID is present in the database.
It raises an exception with SQL error code = -504 Cursor unknown.
The SQL monitor shows that the working SQL is similar to
EXECUTE STATEMENT
TR_HANDLE = 16009724
STMT_HANDLE = 16009152
PARAMS = [ Version 1 SQLd 39 SQLn 39
DATEN.ID = 20067000
while the non-working Locate follows one single Update that seems to use
this different SQL:
SELECT *
FROM DATEN
WHERE DATEN.ID=? /* BIND_0 */
FOR UPDATE
FIELDS = [ Version 1 SQLd 38 SQLn 38
DATEN.ID = 20067000
Any ideas? I don't see why one Locate within many working ones can raise
such an exception. When I catch the exception, the rest of the stuff
continues nicely as though nothing had happened.
A bug maybe?
Cheers,
Tobias
I have a regular SELECT * type of query without even a WHERE. I do a couple
of Locates:
Locate('ID',idnum,[]).
I then do Edit, modify a field, and Post, and on with the next Locate.
Most of the Locates work. But right in the middle of 20 or so working
Locate's, one of them fails even though the ID is present in the database.
It raises an exception with SQL error code = -504 Cursor unknown.
The SQL monitor shows that the working SQL is similar to
EXECUTE STATEMENT
TR_HANDLE = 16009724
STMT_HANDLE = 16009152
PARAMS = [ Version 1 SQLd 39 SQLn 39
DATEN.ID = 20067000
while the non-working Locate follows one single Update that seems to use
this different SQL:
SELECT *
FROM DATEN
WHERE DATEN.ID=? /* BIND_0 */
FOR UPDATE
FIELDS = [ Version 1 SQLd 38 SQLn 38
DATEN.ID = 20067000
Any ideas? I don't see why one Locate within many working ones can raise
such an exception. When I catch the exception, the rest of the stuff
continues nicely as though nothing had happened.
A bug maybe?
Cheers,
Tobias