>
> >so are we going to sully the good reputation of Firebird by now having
> >endless corruption reports? And are we all going to just tell the people who
> >complain of these corruptions that it's all their fault for writing rotten
> >application code?

Classic has run as part of the application process since 1984.
The database code is full of tests for internal consistency that
shut down the connection if a problem is found. After a failed
internal consistency check, nothing more gets written to the database.
Certainly a malicious programmer could use a classic application to
corrupt the database - but why bother? The application has write
access to the file, so it can just scribble on it directly. I
don't know of a reported case of an application corrupting a database
by writing on the memory it shared with the classic library.

Regards,


Ann