One Record Transaction Pattern

Named after helps to implement One Record Transactions

To implement One Record Transaction some kind of generic code is needed, like those needed to assure just one record exists or how to access each attribute. So this pattern generates, given a Transaction, all the code needed to transform it in a One Record Transaction.

This pattern is very convinient for System Parameters implementations.

Given a regular Transaction, the pattern transform it in a One Record Transaction. This TRN must comply with the following prerequisites:

• Must have a Surrogate Key as the Primary Key
• A default rule exists for each other attribute

The pattern generates:

• Modify the TRN to insert the rules for one record assurance.
• For each attribute generates the corresponding access procedure.
  • To do that is necessary to read the default rule of the attribute.