You are not logged in.
Pages: 1
I have an identical unit test performing a Create-Read-Update-Delete sequence (CRUD)
This tries
* Direct mode
* Batched Mode
* Transaction Mode
* Batched+Transaction Mode
And it works great in NamedPipe and MessagingMode.
But... only in HTTP mode, only the Transaction Mode test failes. The three others work perfectly, including batched+transaction mode!
It failes on this line
CheckTrue(SQLWorkbaseRestClient.Update(Rec),'Update record failed');
After some kind timeout (UpdateRecord takes over 5 sec). Any idea where to look? -Most obvious is out NexusDB driver... I have noty had the chance to test this with e.g. Native SQLite3 or Oracle driver.
Hans
Offline
You are right, the first think I would try is to switch to SQLite3 in-memory database, to ensure this is not a generic issue.
On our performance tests with SQLite3 / Oracle / MS SQL / MS Access / ODBC, we did not get such error.
All 4 modes are consistent in behavior, but with diverse timing, of course!
Offline
Pages: 1