Currently validators that check a database will use a different instance of rdbms.Client as application code. This means that validation cannot occur within the same transaction as queries to insert/update data, potentially meaning that data could have changed between validation and insert.
Ensuring that the same instance of rdbms.Client is re-used throughout a request is a specific instance of a more common pattern of 'request scoped resources'.
This issue is:
Identify and implement a common pattern for request scoped resources
Add specific support for request scoped rdbms.Client objects
Currently validators that check a database will use a different instance of rdbms.Client as application code. This means that validation cannot occur within the same transaction as queries to insert/update data, potentially meaning that data could have changed between validation and insert.
Ensuring that the same instance of rdbms.Client is re-used throughout a request is a specific instance of a more common pattern of 'request scoped resources'.
This issue is: