> > We have observed a strange behaviour of Firebird 1.0 concerning
> transactions
> ...
> > Delphi4 + IBO 4.0H
>
> Presumably you've sought help in the IBO group first? You need to
> rule out an IBO problem before you move on to considering the engine
> itself.

Well, I don't think it's the IBO fault. Before IBO we had been using
BDE and we'd been getting exactly the same errors. In fact that was
the reason why we switched from BDE to IBO.
Another hint pointing to FB is that the index page errors occur
only when the server is running on win32, the linux version seems to
work fine.

> > The problem doesn't occur if we execute the query without
> transaction, but
> > still occurs when we include the stored procedure execution in the
> > transaction.
>
> Which would point the finger at your stored procedure, wouldn't it?
> Is it short enough to post here?

It's neither short nor simple ;) If you don't mind, I'll send you
the sample code and a small database to your private e-mail address.
If you don't have IBO, just change the TIB_Query and TIB_StoredProc
components to the standard Delphi's TQuery and TStoredProc.
Besides, it would be pretty strange itself if a stored procedure
would be able to damage index pages in the gdb file, wouldn't it?
I mean, a SQL server is supposed to isolate user activities from
the physical data, so no matter what our code does, the gdb
file should be clean. If it's not, that's a _server_ bug.
The only exception are UDFs. We agree a malicious UDF might do
some harm, but the sample code producing errors doesn't use
any UDFs.

> > We managed to isolate the piece of code causing the error, so if
> anyone
> > would
> > be interested in helping us, we can send an example database and
> client app,
> > which produces the errors.
>
> Do you mean SP code or delphi code? If it's the SP code then by all
> means post it here, if not excessively large -- but first follow up
> in the IBO group if you haven't already.

It's both SP and a small delphi piece of code which invokes the SP.
Like I said, I'll send you a small example which produces errors.
In fact we're very anxious to learn whether the bug affects other
users or it's only us who suffer from it.
So far we haven't even got answers saying 'yes, we observed the same'
or 'no, your sample works fine and gives no errors'.
We do realize the cause might lay somewhere else (we even suspect the
Polish localization of Windows to introduce some incopatibilities)
but first we have to know whether other users are able to replicate
the bug or not.

thank you for your interest

Krzysztof Dyczkowski