(Simplified example) - Inside DoBootStrap action we have the following workflow
#1 3 create actions are executed, to insert 3 item rows “X,Y,Z"
#2 An [action]^ is executed to retrieve ItemByCode, GetItemByCode(“X”) via aggregate widget
^Action: ItemByCode, this action is located inside the same eSpace, it is not an external web service.
In case #2 for SQL Server, expected result - the record value for Item X is to be returned, however in reality it is not returned - why? (no result returned is expected from Oracle but not SQL Server)
Isolation level: READ UNCOMMITTED (SQL Server), means the database should be able to read the database record without first committing the transaction.
Anyone test this? Is there some sort of delay? why SQL Server can not see record itemX?
However in reality, our SQL SERVER behaves like the islotation level has been set to "READ COMMITTED"
(i.e you can not do dirty read without committing).