| Subject | Re: [firebird-support] Is a read-only read committed long running transaction harmfull in FB2.0? |
|---|---|
| Author | Ann W. Harrison |
| Post date | 2006-12-19T22:12:45Z |
danny_vdw wrote:
was not found and wondering if the database is corrupt. That's a side
effect of not blocking garbage collection. Between the time you read
the record and the time you tried to read the blob, someone committed
the deletion or update of the record and both the old record version and
the old blob were deleted. That's not nice, but it's a price of low
consistency transaction modes. You could have the same behavior if
you were depending on, for example, foreign key constraints. When
you read a referencing record, read-committed mode gives you no
guarantee that the referenced record will exist when you try to read it.
Regards,
Ann
>No. You may occasionally see a bad looking error indicating that a blob
> Is a read-only read committed long running transaction harmfull in FB2.0?
>
> Is it blocking OIT/OAT?
> Is it blocking garbage collection?
was not found and wondering if the database is corrupt. That's a side
effect of not blocking garbage collection. Between the time you read
the record and the time you tried to read the blob, someone committed
the deletion or update of the record and both the old record version and
the old blob were deleted. That's not nice, but it's a price of low
consistency transaction modes. You could have the same behavior if
you were depending on, for example, foreign key constraints. When
you read a referencing record, read-committed mode gives you no
guarantee that the referenced record will exist when you try to read it.
Regards,
Ann