Subject | Re: [firebird-support]Index corruption |
---|---|
Author | Fidel Viegas |
Post date | 2009-05-24T09:31:18Z |
On Sun, May 24, 2009 at 5:03 AM, mnavahan <mnavahan@...> wrote:
this? As far as I know, Firebird always raises errors whenever you try
to do something that is not possible. For instance, if your table is
being used by somebody else, then firebird will not let you do any DML
to it. But, I have never seen in case where making a change to one
table affects another. The first thing you should do is trace the
cause of the problem, and not blame the RDBMS for it. Something must
have happened, and that's what you should try to find out. Did you
find what the cause of the problem was? Or you just decided that it
was Firebird's fault?
Firebird may have some hidden bugs that may cause some data
corruption, but that can happen with any open-source software, not to
mention commercial ones. And if I do encounter a problem that corrupts
my database, the first thing I do is try to find a solution, and not
stop using Firebird just because this one problem has occurred.
All the best,
Fidel
>It may be a MUST for you, but don't generalise.
> i have relay same problem about index in FB
> finally decide migrate from firebird to postgresql or oracle(seems must)
>
> 1.if firebird must need grow to enterprise space first solve some backgroundYou have to be more specific about your statement. What sort of index errors?
> problem such ans index errors
>
> 2.if firebird don't support online change of dml then i think is not oneOnce again, what do you mean by this? Do you have pratical examples of
> *enterprise* RDBMS and is only one workgroup DB.....
> if some action (such as change dml) in online DB is wrong FB must do raise
> error and dont do it.... but you think about change table A without any
> relation to table B ...doing some fault in B !
> i dont understand why can not chnge table struct and add own field to table
> A when users only work with table B ?
>
this? As far as I know, Firebird always raises errors whenever you try
to do something that is not possible. For instance, if your table is
being used by somebody else, then firebird will not let you do any DML
to it. But, I have never seen in case where making a change to one
table affects another. The first thing you should do is trace the
cause of the problem, and not blame the RDBMS for it. Something must
have happened, and that's what you should try to find out. Did you
find what the cause of the problem was? Or you just decided that it
was Firebird's fault?
> i do up dramatically with postgresql in other project and have not *any*I haven't had any problems with Firebird either. I am aware that
> problem .....
>
Firebird may have some hidden bugs that may cause some data
corruption, but that can happen with any open-source software, not to
mention commercial ones. And if I do encounter a problem that corrupts
my database, the first thing I do is try to find a solution, and not
stop using Firebird just because this one problem has occurred.
All the best,
Fidel