Subject select ... for update: bug or feature?
Author leu57 <>

though a 'select ... for update' statement is allowed in
SQL and accepted outside an 'declare cursor' statement, it has no
effect on locking the selected row[s] as it has e.g. in ORACLE.

Since I have to connect to FIREBIRD and/or ORACLE from one
application, life would be easier if both would behave in the same

So is this a 'misbehaviour' of firbird supposed to be changed or is
ORACLE (V8) to blame?


Rainer Leopold