Joe has a great handle on this now <g> I believe that this is a good time
and place to run some ideas by the group.
Yanping, the reason why you are seeing this exception is a direct result of
the following implementation detail in the new driver:
Old driver: when you call conn.Commit() we send to the server "IF
TRANCOUNT>0 COMMIT TRAN"
New driver: when you call conn.Commit() we send to the server "COMMIT TRAN"
In the old driver we would ignore your commit call if the server was not in
a transaction, in the new driver we would fail. This behavior is not
consistent with other JDBC drivers that we are aware of and it may make
sense to revert back to the standard way.
The second thing I would like to shop would be moving from the BEGIN TRAN
model to a transaction mode model, this is a request that we have received
from Joe and a number of other customers.
Thoughts, ideas, suggestions?
Angel Saenz-Badillos [MS] Data Programability
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
I am now blogging: http://www.yqcomputer.com/