|Subject||RE: [Firebird-Java] Re: Failure on PreparedStatement|
Yeah, sorry, I was being lazy in the test code. My production code uses explicit commit/rollback, I just left it out of the unit test. It seems to make no difference.
I think you are correct about the blobs. A prepared statement parameter must be parsed differently from when the parameter is embedded in the SQL select string, at least when it comes to blobs.
"SELECT * FROM TableWithBlobs WHERE BlobColumn='FooBar';"
Will succed but
"SELECT * FROM TableWithBlobs WHERE BlobColumn=?;"
-----Original Message-----> Connection con = DriverManager.getConnection( url, info );
From: Roman Rokytskyy [mailto:rrokytskyy@...]
Sent: Friday, April 04, 2003 12:48 PM
Subject: [Firebird-Java] Re: Failure on PreparedStatement
> con.setAutoCommit( false );
In this case you have to correct your code. You cannot close
connection that is not in auto-commit mode without _explicitly_
calling commit() or rollback(). But I will check your test case too,
why does it fail. I suspect that this is because you use BLOBs (even
To unsubscribe from this group, send an email to:
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.