ExecuteBatch commits even if autocommit is false ?

Question

Hello !
Is it true that executeBatch (e.g on PreparedStatement) commits
the changes after running ? We tried using a temporary table
with on "commit delete rows" and fill this table with
executeBatch().
The following Statements seem to find this table empty.
Using normal tables or on commit preserve rows works.
OF course autocommit is false and the temporary table is used
on the same connection.
If it is true, does this violate the jdbc-spec ?
Tested with 8.1.7 Database on sparc and the classes12.zip from
9.0.1
Thanks

Answer 1

SMB 3 in Windows Server 2012 adds the capability to make data transfers secure by encrypting data in-flight, to protect against tampering and eavesdropping attacks. The biggest benefit of using SMB Encryption over more general solutions (such as IPSec) is
that there are no deployment requirements or costs beyond changing the SMB Server settings.
http://blogs.technet.com/b/filecab/archive/2012/05/03/smb-3-security-enhancements-in-windows-server-2012.aspx
http://technet.microsoft.com/en-us/library/jj635714.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.