I am new to Aware IM.
From the getting started guide, I see this as a business rule:
IF
Member IS NEW
THEN
Member.MemberNumber = MAX Member.MemberNumber+1
In a potentially high volume environment, and where the default of database isolation level is set to READ COMMITTED (the best option), using the above logic could potentially assign the same sequential number to multiple object instances, due to dirty reads.
Does anyone know Aware IM protects against this dirty read from happening? Or, alternatively, is there a better design for this type of rule, such that underlying database objects, such as db sequences, are used. Sequences are only assigned in a locked state, and thus will never assign a duplicate value.
