|Subject||Re: Unique Constraints being violated in Firebird|
> Forced Writes Off is unsafe by definition, you mention that you areSo this means we should never allow forced writes to be off?
> using some RC builds but fail to mention the version. FB 1 / 1.5 /Firebird 1 Release
> 2?? Do you notice a performance gain switching it off?
Firebird 1.51 Release
Firebird 2 Release Candidate 1
Firebird 2 Release Candidate 2
> If Firebird happens to write the data to the data page before
> populating the index page (is this possible??) and there is a
> such as hardware failure before the index is updated then I can seeOh I see, so say for instance. We were using classic and RAM runs out,
> this happenning.
as has happenned quite a lot. this would definitely fail.
> Have you (or someone else) been using a tool like xcopy to move theNo this has not been happenning.
> database around, because I can imagine that can quite easily cause
> this. Make sure appropriate exceptions are in place in any virus
> scanning package.
> >Can you be more clear as to what trouble we would get into?
> > Could this be a firebird bug? If so we do have the the GDB from
> > example #1 and a GBK from example #4.
> Rename to gdb to fdb or you will get into trouble in some windows