Natively supporting JSON duality view in a database management system

A method comprising:

• executing a particular database transaction, wherein executing said particular database transaction includes:
• receiving a request to make an update to a database;
• making said update by changing at least one record of a set of records in said database;
• and
• in response to receiving a request to commit the update, determining whether to commit the update or not commit the update at least by:
• in a consistent-read mode, deterministically generating a first version signature based on values in said set of records, wherein generating a first version signature includes applying an undo record generated by said particular database transaction to a data block;
• in a current-read mode, deterministically generating a second version signature based on values in a version of said set of records that reflects uncommitted changes made by said one or more database transactions different than said particular transaction;
• in response to determining that said first version signature and second version signature match, committing said update;
• and
• in response to determining that said first version signature and second version signature do not match, not committing said update.

One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of a process comprising:

• executing a particular database transaction, wherein executing the particular database transaction includes:
• receiving a request to update a JavaScript Object Notation (JSON) object in a JSON Duality View to a particular version of the JSON object received with the request;
• updating a plurality of base records in a database that store values for fields of the JSON object;
• and
• committing the update, wherein committing the update comprises:
• in a consistent-read mode, deterministically generating a first version signature based on the plurality of base records, wherein generating a first version signature includes applying an undo record generated by the particular database transaction to a data block;
• in a current-read mode, deterministically generating a second version signature based on a version of the plurality of base records that reflects uncommitted changes made by one or more other database transactions different than the particular database transaction;
• determining whether the first version signature and second version signature match;
• and
• responsive to the first version signature and the second version signature matching, then committing the update.