Priority: Not Evaluated
Affects Version/s: 5.0.2
Fix Version/s: None
Component/s: SQL Support
QT 5.0.2 + MinGW 4.7 + 32 bits + ODBC driver + Windows 7 (32) + SQL Server 2012 Express
Recently I've got this situation / problem described here (http://qt-project.org/forums/viewthread/28390/) with a small example and after a couple of days, with help from other forum users, I (we) have reached the conclusion that I (we) CAN NOT have transactions with QODBC + SQL Server unless "SqlDatabase::setConnectOptions" supports a "new" parameter "SQL_COPT_SS_PRESERVE_CURSORS=SQL_PC_ON".
Because of that, I would like to leave here a few suggestions/questions for your consideration:
- You could save a lot of time to programmers (like me), by adding a "note" on documentation about this situation (QODBC + SQL Server + Transactions => Close All Cursors => All visible Tables/Grids/Views BLANK)
- Could you add this parameter "SQL_COPT_SS_PRESERVE_CURSORS=SQL_PC_ON" in a future version!? or have an overload "setConnectOptions" (advanced users) to let us call any parameters, even those not implemented?
- Is there a reason for not supporting this parameter, for instance (I'm guessing) that parameter could have (even worst) secondary effects?
- Is there a workaround for using "transactions" with QODBC + SQL Server without "loosing" (BLANK) the information currently presented on screen (visible forms/windows/dialogs with grids/views)?
Thank you for reading.
Any comments or suggestions would be greatly appreciated.