Archives of the TeradataForum

Message Posted: Fri, 12 Sep 2008 @ 16:06:39 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

I didn't follow this thread closely, but in Teradata mode (a.k.a. BTET), COMMIT is not a valid statement.

In ANSI mode, there is no automatic commit. You must explicitly COMMIT; you cannot use BT/ET. (BT results in error 3706.)

In Teradata mode, automatic commit is the default. You must use BT/ET if you wish to put multiple statements in a transaction; you cannot use COMMIT. (COMMIT results in error 3706.)

So why does autoCommit(false) get rid of the error message? Probably because this is a JDBC setting and not a Teradata setting. In other words, autoCommit(true) probably issues COMMIT statements to the DBMS, which are invalid in Teradata mode; autoCommit(false) disables those statements, so everything goes normally.

ANSI mode is evil. I think we can all agree on that.

	<Prev	Next>		<<First	<Prev	Next>	Last>>