Database Constraint Checks Using Versioned Related Records

The patent applies preliminary action by adding version numbers to data records before constraint checks are performed. This allows the system to pre-identify and read the latest version of related data records based on version comparison, eliminating the need for locking mechanisms during the constraint check process. The version number is maintained as a database field that is updated with each data modification, enabling subsequent reads to automatically obtain the correct version without blocking other operations.

The patent applies segmentation by dividing the constraint check process into independent version-comparison operations for each data record rather than locking the entire parent table. Each child record's constraint check independently reads the version number of its corresponding parent record, allowing parallel execution of multiple constraint checks without mutual interference. This segmented approach maintains constraint relationship validity while enabling high throughput through concurrent operations.

The patent replaces the mechanical locking system with a version-number-based identification system. Instead of using share locks that physically block other operations, the system uses version numbers to logically identify and read the latest data records. This substitution eliminates the need for lock acquisition and release operations, allowing multiple transactions to concurrently read and write data without interference, thereby maintaining data integrity through version comparison rather than mechanical blocking.