Mike,

At 01:29 AM 20/11/2003 +0000, you wrote:

>Hi everyone,
>
>I'm reposting this here per the advice of people on the main
>firebird list.
>
>I'm having a problem that is proving difficult to troubleshoot.
>
>Platform:
>
>Windows XP
>Firebird 1.5 RC6
>Jaybird 1.0.1
>
>I'm connecting to the database fine and executing stored procedures
>via CallableStatements. They complete without any difficulty, but
>for some reason aren't committing to the database. Looking at the
>tables from a second database tool shows no activity, yet I can edit
>the data from my Java connection as long as I don't restart my
>application.
>
>I've tried running setAutoCommit(true) explicitly when the
>connection is first created to no avail. Inside the debugger (I use
>Eclipse for Java) I've turned off autoCommit after pausing the
>application through breakpoints, run the procedure, committed, and
>then turned autoCommit on again, and it works fine after that until
>I restart the application.
>
>Anybody run into anything similar?

I'll let the Java bods answer the application side of your question, but my
question is this:

When you are using this "other tool" to monitor the database activity, are
you committing the tool's old view before requerying to check on new
activity? Everything in Firebird happens in transactions. So - you open a
transaction in the other tool, and then run your Java application
code...the other tool is still looking at database state *before* the Java
app committed its work. It won't see what your Java app did until you
commit that old transaction and start a new one.

Helen