Hi Helen

I have sent an e-mail to your e-mail account.


Of course I am interested in the FB 1.5.1. It has been torturing me
for this last year. I am frustrated because I could not give a
response to the customers.

In any case, I am a little sceptical with FB 1.5.1 because I had the
same problem using FB 1.0. Then, when I installed FB 1.5, I believed
that the bug was fixed, everything worked ok and seemingly the
errors had disappeared. The reality is that the bug was hidden and
latent. As you have seen, this bug appears only with a combination
of queries and a specific view. If you modify the view or the
combination of queries, everything works ok.
I mean that the detonating of the bug is not clear, it is very
confused and depends on a lot of factors. Any modification (view,
queries, FB version, ...) can hidde the bug, but the bug exists.

Maybe now this bug has been fixed, I would like to try it. Please,
where I can find the version?

Thank you for your help, now I see a little of light.

--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
> At 11:24 AM 1/06/2004 +1000, I wrote:
>
> > >sorry to jump in at this late point in the thread, but if the
server
> > >crashes then the test case will be of use for the Fb developers
as well
> > >as Jason, I believe.
> >
> >I completely agree. But first, it will be most useful to find
out why
> >TIBOQuery causes this behaviour, while TIB_Cursor doesn't. In
the middle
> >is TIB_Query, which I'll test today.
> >
> >A test case demonstrating all three will help Jason to isolate
exactly what
> >it is about the client layer that is capable of crashing the
server, i.e.
> >what API function is broken. It seems to relate to the default
transaction
> >(gds__trans) that one could guess might have been broken on the
client side
> >of the y-valve...I'm not familiar enough with the <default
transaction>
> >mechanism to know whether the TDataset architecture handles it
differently
> >to native IBO.
> OK, last night I made five test cases with the kokkok test data,
with a
> variety of statement objects and transaction options. The
Firebird 1.5
> crashing behaviour was consistent with all mixes except when
TIB_Cursors
> were used.
>
> Today I ran all of the test cases under Firebird v.1.5.1 (the
release
> candidate we're currently working on) and the crashing behaviour
has
> disappeared.
>
> There will be a bug description and fix report in the v.1.5.1
release notes.
>
> "Mr Kokkok", please contact me if you're interested in downloading
this
> pre-release and testing it. (It would also be nice to know your
name...)
>
> Helen