Hi,

As an addition to Helen's email, here's some JayBird specifics:

> Is
> it possible to trigger an error at the prepareStatement method just
> like the "? IS NULL" condition?

JayBird does not trigger such errors, it just interprets the errors returned
by a server. The "unrecognized transaction" can be considered a bug in
JayBird, since it hides the actual error reported by a server. Though it is
not very easy to fix it.

> I found it confusing that some queries did work without failure and some
> didn't related to a PRIMARY KEY index that was or wasn't there.

I agree, but this has something to do with a server code, not to JayBird.

> A workaround would probably be to use some sort of checksum to see
> if there where changes inside BLOB fields. Does the blob_col LIKE ?
> condition work like expected?

There is another issue with JayBird. At present the blob parameters in WHERE
clause are useless, since driver first creates a new blob in database and
then sends its ID for comparison. According to JDBC specification you should
be able to use setObject(int, Object, int) method to tell which type of
parameter you want to send to server, but it is not currently supported.


Roman