Subject | Re: [IBO] serious design problem: update queries |
---|---|
Author | Svein Erling Tysvaer |
Post date | 2003-07-21T08:31:14Z |
Hi Leon! Helen and Lester have answered most of your questions and I only
have one little comment:
mail so indicates): Firebird has only got row level locking, not field
level (please correct if it exists and is a feature unknown by me). Hence,
if one user change any field of a record, then there is no way another
transaction can change any field of that record until the transaction that
updated the record is committed or rolled back.
Set
have one little comment:
>But what is the correct solution for this problem using IBobjects? Is thereAssuming you meant "fields" and not "records" (the preceeding part of your
>a way to only put "changed" records into the update statement.
mail so indicates): Firebird has only got row level locking, not field
level (please correct if it exists and is a feature unknown by me). Hence,
if one user change any field of a record, then there is no way another
transaction can change any field of that record until the transaction that
updated the record is committed or rolled back.
Set