> Hi we have quite a mystifying problem. I'm not sure if it is with
> firebird or the jdbc driver. We're using FB 1.5.5., java code and jdbc
> 2.1.6. Lengthy post coming up!
>

<SNIP>

> -
> I disconnect from the database then reconnect THEN create the
> PreparedStatement and start processing, everything works perfectly (so
> I
> know the SQL is all right).
> I've also found that if I create a new database (via a data pump) and
> apply all constraints and the new trigger (without the old one first,
> then dropping it), then the PreparedStatement also works correctly in
> this case.
>
> So can someone please tell me what is going wrong here.
> - When dropping a trigger and creating a new one, do I need to
> disconnect in between?

Yes, we just had a thread today along these lines. With most PSQL changes,
clients who are already connected will continue to use "old" PSQL code
because this is seen as an important way to maintain data consistency per
user.

> - Is this a bug in Firebird or the JDBC driver? Is the JDBC driver
> getting confused after the trigger is dropped and a new one created?
>
> It's really important for us to know what is going on here. We have a
> large number of clients and we need to understand the implications of
> this behaviour. Any ideas?
>
> Thanks, Phil
>

All structural changes to databases should really be done without anyone
connected (other than the database creator/designer/owner doing the
changes).
Alan