Hi,

> I can sort of understand that the Classic server cannot lock the file, creating separate processes. But as I understand SuperClassic is a single process creating multiple threads and locking should therefore be possible, I think, but maybe not.

It could, but SuperClassic, even though it is single-process, follows the Classic tradition of letting other servers connect as well. Therefore, it doesn't take an exclusive lock on the database.

An advantage of this approach is e.g. that a regular server (as long as it's not a Superserver) and one or more embedded servers (which have SuperClassic architecture as of Firebird 2.5) can access a database simultaneously.


Paul Vinkenoog