Re: [Dbi-interbase-devel] report on 20.3

[Mark D. A. <md...@di...>]

more information --

earlier today i also got the "lock conflict on no wait transaction" message even from
isql, so the new DBD-InterBase was not the only one getting it.

i just re-ran my script, and i got:
no permission for read-write access to database /home/interbase/data/snap/snap4.gdb

and guess what? i got the same thing from isql just now also! like this:
   SQL> connect /home/interbase/data/snap/snap4.gdb;
   Statement failed, SQLCODE = -551
   no permission for read-write access to database /home/interbase/data/snap/snap4.gdb

however, my various ibconsole-equivalents (ib_wisql, marathon, etc.) have no problem connecting.
also, my very same perl script using the old DBD::InterBase (based on ibperl) works fine.

so what is it that isql and the new InterBase.pm have in common,
and that ib_wisql and the old InterBase.pm have in common?

must have something to do with transaction parameters, which is what got me started
on this thread anyway :). hopefully soon InterBase.pm will expose complete control
over transaction parameters, so i can actually experiment with that, rather than
poking at things with a very long stick....

btw, i also tracked down what was responsible for the "lock conflict" message --
it was due to connecting to the database with ibobject's IB_WISQL.
it must open up a transaction with some obnoxious transaction parameters
as soon as it connects.
i've looked for further documentation on both the messages above, and not
succeeded.

-mda