Subject | Re: [ib-support] gbak error (2nd post) |
---|---|
Author | David K. Trudgett |
Post date | 2002-02-10T23:10:55Z |
On Friday 2002-02-08 at 08:40:19 +0100, Duilio Foschi wrote:
database through its paces (the laws of permutation work against test
suites picking up subtle bugs that may only appear in very unusual
circumstances).
with system tables, though.
some version of InterBase being used in US M1 tanks. Every time the
tank's cannon fired, the resulting electrical surge would crash most
of the on-board systems, including the on-board computer running
InterBase. InterBase would always jump back into active service after
system re-initialisation. If InterBase can deal with battlefield
conditions, a little CTRL-F2 should be no problem at all ;-)
Cheers,
David Trudgett
> I mostly used WISQL and QuickDesk.I suspect that doing a lot of that sort of thing would put any
>
> I played a lot with the db: deleting and re-creating constraints, fields
> and whole tables, etc
database through its paces (the laws of permutation work against test
suites picking up subtle bugs that may only appear in very unusual
circumstances).
>SQL should be safe. I don't know if QuickDesk does any funny stuff
> But I always used SQL or the visual i/f of QuickDesk
with system tables, though.
> One thing comes to mind: sometimes I abruptly halted a transaction fromIt shouldn't in theory. There's the story (a bit of folklore, now) of
> Delphi using CTRL-F2: could this corrupt the db ?
some version of InterBase being used in US M1 tanks. Every time the
tank's cannon fired, the resulting electrical surge would crash most
of the on-board systems, including the on-board computer running
InterBase. InterBase would always jump back into active service after
system re-initialisation. If InterBase can deal with battlefield
conditions, a little CTRL-F2 should be no problem at all ;-)
Cheers,
David Trudgett