Is It necessary To Call SQLFreeStmt(...,SQL_CLOSE) Prior To A Rollback

Question

If you have a program that does the following:
1) Opens a database connection.
2) Prepares a SQL statement.
3) Binds columns to the SQL statement.
4) Executes either an insert, update, or delete statement.
5) An an error is encountered executing the statement, say unique primary key contraint failure.
6) The code detects this error and issues a rollback followed by a commit.
7) The code processes another transaction repeating from step 3 onward (using the same database connection, prepared SQL statement, etc.)
After a rollback, is it still necessary to issue a SQLFreeStmt(..., SQL_CLOSE) on a statment, prior to rexecuting the statement?
Thanks.

Answer 1

It is never necessary to call SQLFreeStmt(...,SQLCLOSE) for a handle used for DML. The SQL_CLOSE option simply closes any curtsor associated with the handle; Only statements that return a result set (such as SELECT) ever need to be closed in this way. Note that in TimesTen both COMMIT and ROLLBACK close all cursors associated with all handles for the connection. Hence if you are going to commit or rollback anyway it is not necessary to SQL_CLOSE handles for SELECTs either.
So, in your example it is not necessary to issue the SQL_CLOSE since you are doing DML. The close will have no effect and is just a waste of cycles. Also, there is no need to execute a commit after the rollback. Again it does nothing and just wastes CPU cycles.
Chris