No problem then, thanks for your feedback.

Regards,
Deepak

--- On Wed, 3/3/10, Dimitry Sibiryakov <sd@...> wrote:

From: Dimitry Sibiryakov <sd@...>
Subject: Re: [firebird-tools] Technology to improve Firebird Reliability
To: firebird-tools@yahoogroups.com
Date: Wednesday, 3 March, 2010, 12:23







 









03.03.2010 13:20, Deepak Saldanha wrote:

> Sure, am talking about database errors originating from the backend(from

> Firebird), cascading to the front end and then ultimately corrupting the

> backend(Firebird) from subsequent queries.



Firebird has full support for ACID transaction, so database is always

in consistent state.



> --- On *Wed, 3/3/10, Dimitry Sibiryakov /<sd@ibphoenix. com>/* wrote:

>

>

> From: Dimitry Sibiryakov <sd@ibphoenix. com>

> Subject: Re: [firebird-tools] Technology to improve Firebird Reliability

> To: "Deepak Saldanha" <saldanhadeepak@ yahoo.co. uk>

> Date: Wednesday, 3 March, 2010, 12:14

>

> 03.03.2010 12:32, Deepak Saldanha wrote:

> > Not sure if IBSurgeon is able to detect logical errors, that

> mostly go

> > unnoticed and results in wrong data cascading to the front end?

> Errors

> > are prevalent in most databases due to complexity and infact

> about 50%

> > of errors go unnoticed and do not result in the DB crashing. We have

> > undertaken tests to prove this.

>

> Firebird is back-end, not frond-end, thus such errors are out of scope.



--

SY, SD.























[Non-text portions of this message have been removed]