U++ forum: Welcome to the forum

Re: OleDB + parameters = problem [message #19820 is a reply to message #19813]

Sat, 24 January 2009 17:58

Novo
Messages: 1430
Registered: December 2006

Ultimate Contributor

luzr wrote on Fri, 23 January 2009 05:59

Anyway, it seems like DDL does not have such bad effect on precompiled statements after all:

I checked my code.

In case of DDL statement and:

ADO - (I was using it with JET and MSSQL Server) I commit transaction and clear statement cache.

SQLITE - clear statement cache and finalize current statement (I'm using old API).

Interbase/Firebird - clear statement cache, rollback transaction, execute DDL, commit transaction. (This database has slightly different transaction model).

ODBC � rollback transaction, execute DDL, commit transaction. Cache is not affected. Probably, this is a bug, or it was tested only with MS SQL Server.

ORACLE - clear statement cache, execute DDL, mark all open statements as invalidated by DDL (they should be prepared again).

CTLIB (Sybase and MS SQL Server) � no problem with cache.

Microsoft has different APIs to work with MS SQL Server. Prepare-Bind-Execute model is implemented using special stored procedures, which are often called by a high-level API. You can check that in FreeTDS ODBC driver. It is open-source.

Regards,
Novo

Report message to a moderator