Abstract: Systems and methods for controlling blood pressure via electrical stimulation of the heart are disclosed. Embodiments may include at least two different stimulation patterns, each configured to reduce blood pressure to a different degree, and may alternate between stimulation patterns based on the need of a patient, for example, alternating between day and night or between periods of strenuous and light activity. Some embodiments may take advantage of a slow baroreflex response that occurs after treatment is stopped, suspending treatment for extended periods, and then resuming treatment before blood pressure levels reach pretreatment values. Embodiments may control blood pressure by controlling atrial pressure and atrial stretch.

Abstract: A system and methods for implementing a materialized view for a query are provided. The query system includes a database that includes a base table. The base table can include a set of data. The query system also includes a materialized view associated with a portion of the set of data, and a MVQR component to translate each of a range predicate of the materialized view and a range predicate of a query into a canonical range representation (CRR) format in materialized view metadata and query metadata, respectively, to enable the query to search the materialized view.

Abstract: A system and methods for implementing a materialized view for a query are provided. The query system includes a database that includes a base table. The base table can include a set of data. The query system also includes a materialized view associated with a portion of the set of data, and a MVQR component to translate each of a range predicate of the materialized view and a range predicate of a query into a canonical range representation (CRR) format in materialized view metadata and query metadata, respectively, to enable the query to search the materialized view.

Abstract: A method of performing a database join is provided herein. The method includes receiving a query. The query may specify an update for a table. The method further includes determining that the table is associated with a subscriber. Additionally, the method includes generating an audit log for the update within the table. The audit log may comprise the update.

Abstract: The disclosed embodiments relate to a system for refreshing a table to produce a refreshed table. The system may include a refresh log that may contain a plurality of entries that each comprise an epoch identifier. The system may also include a refresh manager that may be adapted to perform a refresh operation on the table using entries that have corresponding epoch identifiers.

Abstract: The disclosed embodiments relate to an apparatus for performing refresh operations. The apparatus comprises a base table having a first set of data entries, a materialized view having a second set of data entries that are associated with the first set of data entries in the base table. Further, a refresh log contains a set of changes that were made to the base table since the materialized view was last refreshed. A module is utilized to perform a refresh operation on the materialized view using the second set of data entries. The module is configured to access the refresh log and the materialized view, calculate delta values from the set of changes in the refresh log and the second set of data entries, apply the delta values to second set of data entries in the materialized view, and provide the delta values to a delta adaptation module for updating a second materialized view.

Abstract: The disclosed embodiments relate to a system and method for refreshing a materialized view that is at least in part derived from a table. The system may be adapted to provide availability of the table and the materialized view while the materialized view is being refreshed. The system may include a refresh log that contains a plurality of entries, each of the plurality of entries corresponding to a change in the table, each of the plurality of entries comprising an epoch identifier.

Abstract: The disclosed embodiments may relate to a system for performing logical range logging. The system may include a refresh log that may contain entries and a database management system (“DBMS”) that may read the refresh log and employ buffers to perform a refresh operation on a table using the entries. The DBMS may determine if a last row of a previous one of the plurality of buffers is allocated and assign a status attribute for the last row of the previous buffer if the previous buffer is allocated. The DBMS may determine if a current row in a current buffer is a last row to be inserted into the table as part of the refresh operation.

Abstract: The disclosed embodiments relate to a system for refreshing a table to produce a refreshed table. The system may include a refresh log that may contain a plurality of entries that each comprise an epoch identifier. The system may also include a refresh manager that may be adapted to perform a refresh operation on the table using entries that have corresponding epoch identifiers.

Abstract: A method for executing before-triggers in an active database. A tree of actions is constructed for each activated before-trigger and a tree of operators is constructed for the statement that activates the trigger. A table affecting operator that is included in the activating statement is removed from the statement tree and a temporary execution operator is formed from any remaining actions of the activating statement. The temporary execution operator and the activated before-triggers are then included in an insertion operator that is configured to send updated rows into a temporary table. The table affecting operator is then interconnected to execute subsequent to the insertion operator. Any activated row-after and statement-after triggers are interconnected to execute subsequent to the execution of the table-affecting operator.

Abstract: A method for executing after-triggers in an active database. A tree is constructed for each after-trigger and an operator tree is constructed for the statement that activates the trigger. The method joins each of the trees for the activated row-after triggers to the operator tree for pipelined execution with the operator tree. The trees for the activated row-after triggers form a group and each of the trees within the group execute in parallel with each other. The method joins trees for activated statement-after triggers to the operator tree for execution subsequent to the execution of the operator tree, the statement after trigger trees receiving rows from a temporary table that accumulates affected rows from the operator tree. Trees for activated statement after triggers form a group and each of the trees within the group execute in parallel with each other.

Abstract: A method for executing after-triggers in an active database. A tree is constructed for each after-trigger and an operator tree is constructed for the statement that activates the trigger. The method joins each of the trees for the activated row-after triggers to the operator tree for pipelined execution with the operator tree. The trees for the activated row-after triggers form a group and each of the trees within the group execute in parallel with each other. The method joins trees for activated statement-after triggers to the operator tree for execution subsequent to the execution of the operator tree, the statement after trigger trees receiving rows from a temporary table that accumulates affected rows from the operator tree. Trees for activated statement after triggers form a group and each of the trees within the group execute in parallel with each other.

Abstract: A method for executing triggers in an active database. An operator tree is formed for the activating trigger and the activated triggers are identified. Each trigger has a creation time stamp. Conflicting triggers are determined based on the tables accessed by the activated triggers. Two or more parallel groups are formed such that conflicting triggers are placed into a different parallel groups and non-conflicting triggers are contained within a parallel group. The parallel groups are interconnected for sequential execution, the order of execution of the parallel groups being based on the creation time stamps of conflicting triggers. The parallel groups are then connected to the operator tree and, if possible, a parallel group containing row triggers is connected to execute in a pipelined fashion with the operator tree of the activating statement.

Abstract: A method for executing before-triggers in an active database. A tree of actions is constructed for each activated before-rigger and a tree of operators is constructed for the statement that activates the trigger. A table affecting operator that is included in the activating statement is removed from the statement tree and a temporary execution operator is formed from any remaining actions of the activating statement. The temporary execution operator and the activated before-triggers are then included in an insertion operator that is configured to send updated rows into a temporary table. The table affecting operator is then interconnected to execute subsequent to the insertion operator. Any activated row-after and statement-after triggers are interconnected to execute subsequent to the execution of the table-affecting operator.

Abstract: A method for executing triggers in an active database. An operator tree is formed for the activating trigger and the activated triggers are identified. Each trigger has a creation time stamp. Conflicting triggers are determined based on the tables accessed by the activated triggers. Two or more parallel groups are formed such that conflicting triggers are placed into a different parallel groups and non-conflicting triggers are contained within a parallel group. The parallel groups are interconnected for sequential execution, the order of execution of the parallel groups being based on the creation time stamps of conflicting triggers. The parallel groups are then connected to the operator tree and, if possible, a parallel group containing row triggers is connected to execute in a pipelined fashion with the operator tree of the activating statement.

Abstract: A method for executing after-triggers in an active database. A tree is constructed for each after-trigger and an operator tree is constructed for the statement that activates the trigger. The method joins each of the trees for the activated row-after triggers to the operator tree for pipelined execution with the operator tree. The trees for the activated row-after triggers form a group and each of the trees within the group execute in parallel with each other. The method joins trees for activated statement-after triggers to the operator tree for execution subsequent to the execution of the operator tree, the statement after trigger trees receiving rows from a temporary table that accumulates affected rows from the operator tree. Trees for activated statement after triggers form a group and each of the trees within the group execute in parallel with each other.