Data models containing host language embedded constraints
First Claim
1. A computer-implemented method comprising:
- receiving, on an in-memory database engine, a first event handler containing code configured to validate a first entity comprising an object in an in-memory database and including a constraint derived from a second entity of an Entity-Relationship Model defined by an extension of Structured Query Language to include an association type comprising a first parameter clause specifying a cardinality, and a second parameter clause specifying a foreign key, wherein an application configured to manage the in-memory database and the first event handier are in a host language different than SQL;
identifying, by the in-memory database engine and according to the first event handler, a built-in event associated with the first entity;
registering, by the in-memory database engine, the first event handler to the built-in event;
evaluating the constraint by referencing the cardinality and the foreign key,wherein the application automatically calls the first event handler when the built-in event is triggered; and
wherein the in-memory database engine includes at least one service, data definition, or data processing based on an Entity-Relationship Model and at least one service, data definition, or data processing based on a Relational Model.
2 Assignments
0 Petitions
Accused Products
Abstract
Techniques are described for expressing a constraint in a host language. A constraint can be defined in the host language as an event handler. The event handler can be registered to a built-in event associated with an object of the database that the constraint is intended to validate. When the object triggers the built-in event, the event handler is called to execute the constraint. Exemplary built-in events include onSave (trigger the event when the object is saved), onValidate (trigger the event when an explicit call to validate the object is detected), onInsert (trigger the event when the object is inserted), onUpdate (trigger the event when the object is updated), and onCheckBeforeSave (trigger the event when the object is checked prior to saving).
177 Citations
20 Claims
-
1. A computer-implemented method comprising:
-
receiving, on an in-memory database engine, a first event handler containing code configured to validate a first entity comprising an object in an in-memory database and including a constraint derived from a second entity of an Entity-Relationship Model defined by an extension of Structured Query Language to include an association type comprising a first parameter clause specifying a cardinality, and a second parameter clause specifying a foreign key, wherein an application configured to manage the in-memory database and the first event handier are in a host language different than SQL; identifying, by the in-memory database engine and according to the first event handler, a built-in event associated with the first entity; registering, by the in-memory database engine, the first event handler to the built-in event; evaluating the constraint by referencing the cardinality and the foreign key, wherein the application automatically calls the first event handler when the built-in event is triggered; and wherein the in-memory database engine includes at least one service, data definition, or data processing based on an Entity-Relationship Model and at least one service, data definition, or data processing based on a Relational Model. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions for:
-
receiving, on an in-memory database engine, a first event handier containing code configured to validate a first entity comprising an object in an in-memory database and including a constraint derived from a second entity of an Entity-Relationship Model defined by an extension of Structured Query Language (SQL) Language to include an association type comprising a first parameter clause specifying a cardinality, and a second parameter clause specifying a foreign key, wherein an application configured to manage the in-memory database and the first event handler are in a host language different than SQL; identifying, by the in-memory database engine and according to the first event handler, a built-in event associated with the first entity; and registering, by the in-memory database engine, the first event handler to the built-in event; evaluating the constraint by referencing the cardinality and the foreign key, wherein the application automatically calls the first event handler when the built-in event is triggered; and wherein the in-memory database engine includes at least one service, data definition, or data processing based on an Entity-Relationship Model and at least one service, data definition, or data processing based on a Relational Model. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A computer system comprising:
-
ail in-memory database engine; and a non-transitory computer readable medium having stored thereon one or more programs, which when executed by the in-memory database engine, causes the in-memory database engine to; receive a first event handler containing code configured to validate a first entity comprising an object in an in-memory database including a constraint derived from a second entity of an Entity-Relationship Model defined by an extension of Structured Query Language (SQL) Language to include an association type comprising a first parameter clause specifying a cardinality, and a second parameter clause specifying a foreign key, wherein an application configured to manage the in-memory database and the first event handier are in a host language different than SQL; identify according to the first event handler, a built-in event associated with the first entity; register the first event handier to the built-in event; and evaluate the constraint by referencing the cardinality and the foreign key, wherein the application automatically calls the first event handler when the built-in event is triggered; and wherein the in-memory database engine includes at least one service data definition, or data processing based on an Entity-Relationship Model and at least one service, data definition, or data processing based on a Relational Model. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification