> -----Original Message-----
> From: Firebird-general@yahoogroups.com
> [mailto:Firebird-general@yahoogroups.com] On Behalf Of Roger Vellacott
> Sent: Viernes, 12 de Junio de 2009 7:44
>
> I have the snapshot, and it solves the problem. It just seemed a bit
> weird to us that the only way we can have a stable version of FB is to
> use what, (cf Helen's reply), is an untested, and therefore
> potentially
> unstable, snapshot build, which was loaded to the website only 7 days
> after the official release.

From a POV of a app devs that needs to solve that problem, it may look
weird, but...

> So from our point of view, the official, stable release is unstable.
> And the unofficial, unstable release is stable. I thought
> someone might
> want to do something about this.

Typically for me, "unstable" means "it crashes". There are a lot of
bugchecks that are implemented as a security measure and don't mean
necessarily that the engine is trashed internally or that the db is
destroyed.

A bugcheck message usually is an indication that the code found a condition
not expected by the developer, then to avoid further damage, operations
against the db are stopped, until you close all connections to it. Some of
them are serious, like not being able to find a db page with txn info or not
being able to find the previous version of a record. Other are related to
expressions evaluation and in most cases don't cause corruption.

C.