18115629. FRAMEWORK AND METHOD FOR CONSISTENT CROSS-TIER DATA VALIDATION simplified abstract (Oracle International Corporation)

From WikiPatents
Jump to navigation Jump to search

FRAMEWORK AND METHOD FOR CONSISTENT CROSS-TIER DATA VALIDATION

Organization Name

Oracle International Corporation

Inventor(s)

Tirthankar Lahiri of Palo Alto CA (US)

Srikrishnan Suresh of Belmont CA (US)

Beda Christoph Hammerschmidt of Palo Alto CA (US)

Adrian Daniel Popescu of Zurich (CH)

Jesse Kamp of Castro Valley CA (US)

Zhen Hua Liu of San Mateo CA (US)

FRAMEWORK AND METHOD FOR CONSISTENT CROSS-TIER DATA VALIDATION - A simplified explanation of the abstract

This abstract first appeared for US patent application 18115629 titled 'FRAMEWORK AND METHOD FOR CONSISTENT CROSS-TIER DATA VALIDATION

Simplified Explanation

A computer analyzes a relational schema of a database to generate a data entry schema and encodes the data entry schema as JSON. The data entry schema is sent to a database client so that the client can validate entered data before the entered data is sent for storage. From the client, entered data is received that conforms to the data entry schema because the client used the data entry schema to validate the entered data before sending the data. Into the database, the entered data is stored that conforms to the data entry schema. The data entry schema and the relational schema have corresponding constraints on a datum to be stored, such as a range limit for a database column or an express set of distinct valid values. A constraint may specify a format mask or regular expression that values in the column should conform to, or a correlation between values of multiple columns.

  • The innovation involves a computer analyzing a relational schema to generate a data entry schema.
  • The data entry schema is encoded as JSON and sent to a database client for data validation before storage.

Potential Applications

The technology can be applied in various industries such as healthcare, finance, and e-commerce for efficient data validation and storage processes.

Problems Solved

1. Ensures data integrity by validating entered data before storage. 2. Streamlines the data entry process by providing a structured schema for data validation.

Benefits

1. Reduces errors in data entry. 2. Improves database efficiency by storing only validated data. 3. Enhances data security by ensuring data consistency.

Potential Commercial Applications

Optimizing data management systems with automated data validation processes.

Possible Prior Art

Similar technologies may exist in the field of database management systems, but the specific approach of using a data entry schema generated from a relational schema for data validation may be novel.

Unanswered Questions

How does the technology handle complex relational databases with multiple interdependent tables and constraints?

The article does not delve into the specifics of handling complex relational databases with multiple interdependent tables and constraints. Further research or a detailed explanation from the patent application would be needed to address this question.

What are the potential limitations or drawbacks of using this technology in real-world database systems?

The article does not discuss any potential limitations or drawbacks of using this technology in real-world database systems. Additional information or case studies would be necessary to explore this aspect further.


Original Abstract Submitted

A computer analyzes a relational schema of a database to generate a data entry schema and encodes the data entry schema as JSON. The data entry schema is sent to a database client so that the client can validate entered data before the entered data is sent for storage. From the client, entered data is received that conforms to the data entry schema because the client used the data entry schema to validate the entered data before sending the data. Into the database, the entered data is stored that conforms to the data entry schema. The data entry schema and the relational schema have corresponding constraints on a datum to be stored, such as a range limit for a database column or an express set of distinct valid values. A constraint may specify a format mask or regular expression that values in the column should conform to, or a correlation between values of multiple columns.