Usage of Filters for Database-Level Implementation of Constraints
Embodiments relate to methods and apparatuses implementing database-level consistency checking in a declarative manner. A consistency engine within the database layer may access one or more consistency rules in the form of a table or executable program code. Based upon application of these consistency rules to records comprising combinations of data characteristics, the consistency engine may determine the validity or invalidity those records. Consistency rules may implement a ‘check’ method, and also a ‘derive’ method allowing derivation of data characteristics (targets) in a record from other characteristics (sources) in the record. Filters may be used to split data records to sets of records having all fields assigned, and those having ‘not assigned’ fields. Consistency rules used for derivation methods can be nested. Also, in certain embodiments a consistency engine may use filtering techniques for constraint checking including multi-level derivations in a declarative way.
1 . A computer-implemented method comprising:
causing a database engine in a database layer to receive an instruction from an application layer to create plan data;
causing a consistency engine in the database layer to declare a validity or an invalidity of the plan data based upon a consistency rule accessed in the database layer;
where the consistency engine declares a validity of the plan data, causing the database engine to write the plan data to a persistency layer; and
where the consistency engine declares an invalidity of the plan data, causing the database engine to not write the plan data to the persistency layer.
2 . A method as in claim 1 wherein the consistency engine declares the validity based upon a filtering.
3 . A method as in claim 2 wherein the filtering comprises automatically declaring the validity where a field is not assigned.
4 . A method as in claim 2 wherein the data is derived from a source characteristic, and the filtering comprises automatically declaring the validity where a field of the source characteristic is not assigned.
5 . A method as in claim 2 wherein the data is derived in multiple levels from a target characteristic, and the filtering comprises automatically declaring the validity where a field of the target characteristic is not assigned.
6 . A method as in claim 1 wherein the consistency engine declares the invalidity based upon a filtering of a target field collision.
7 . A method as in claim 1 wherein the consistency rule comprises a table or executable program code.
8 . A non-transitory computer readable storage medium embodying a computer program for performing a method, said method comprising:
causing a database engine in a database layer to receive an instruction from an application layer to create plan data;
causing a consistency engine in the database layer to declare a validity or an invalidity of the plan data based upon a consistency rule accessed in the database layer;
where the consistency engine declares a validity of the plan data, causing the database engine to write the plan data to a persistency layer; and
where the consistency engine declares an invalidity of the plan data, causing the database engine to not write the plan data to the persistency layer.
9 . A non-transitory computer readable storage medium as in claim 8 wherein the consistency engine declares the validity based upon a filtering.
10 . A non-transitory computer readable storage medium as in claim 9 wherein the filtering comprises automatically declaring the validity where a field is not assigned.
11 . A non-transitory computer readable storage medium as in claim 9 wherein the data is derived from a source characteristic, and the filtering comprises automatically declaring the validity where a field of the source characteristic is not assigned.
12 . A non-transitory computer readable storage medium as in claim 9 wherein the data is derived in multiple levels from a target characteristic, and the filtering comprises automatically declaring the validity where a field of the target characteristic is not assigned.
13 . A non-transitory computer readable storage medium as in claim 8 wherein the consistency engine declares the invalidity based upon a filtering of a target field collision.
14 . A non-transitory computer readable storage medium as in claim 8 wherein the consistency rule comprises a table or executable program code.
15 . A computer system comprising:
one or more processors;
a software program, executable on said computer system, the software program configured to:
cause a database engine in a database layer to receive an instruction from an application layer to create plan data;
cause a consistency engine in the database layer to declare a validity or an invalidity of the plan data based upon a consistency rule accessed in the database layer;
where the consistency engine declares a validity of the plan data, causing the database engine to write the plan data to a persistency layer; and
where the consistency engine declares an invalidity of the plan data, causing the database engine to not write the plan data to the persistency layer.
16 . A computer system as in claim 15 wherein the consistency engine declares the validity based upon a filtering.
17 . A computer system as in claim 16 wherein the filtering comprises automatically declaring the validity where a field is not assigned.
18 . A computer system as in claim 16 wherein the data is derived from a source characteristic, and the filtering comprises automatically declaring the validity where a field of the source characteristic is not assigned.
19 . A computer system as in claim 16 wherein the data is derived in multiple levels from a target characteristic, and the filtering comprises automatically declaring the validity where a field of the target characteristic is not assigned.
20 . A computer system as in claim 15 wherein the consistency engine declares the invalidity based upon a filtering of a target field collision.