Subject | Re: [firebird-support] Recurring database corruption |
---|---|
Author | Helen Borrie |
Post date | 2006-08-11T07:39:55Z |
At 05:18 PM 11/08/2006, you wrote:
which the application is written - typically stateless web
applications - not a friendly climate to have forced writes turned
off (even if it were NOT Windoze).
from spoiling perfection? :-)
Nigel has a point, too - don't mix DDL and DML - though it didn't
*appear* that was part of the changed conditions that are breaking
their databases.
./heLen
> > Given the kind of conditions people usually write PHP applicationsNot talking about what the *application* does, but the conditions for
> > for, this risky configuration has now become distinctly
> > life-threatening....
>
>
>What action done by an client application can cause data corruption?
which the application is written - typically stateless web
applications - not a friendly climate to have forced writes turned
off (even if it were NOT Windoze).
>In Client-Server operation the server should prevent the client fromTrue, and not just for client/server. But what can prevent humans
>corrupting the database.
from spoiling perfection? :-)
Nigel has a point, too - don't mix DDL and DML - though it didn't
*appear* that was part of the changed conditions that are breaking
their databases.
./heLen