Database Reference
In-Depth Information
API
Proxy Service
Generating Query
Single Table
Function
Master-details
Relationship Function
Left Join
Function
Union
Function
Query Options
Select Clause
Targeted Tables
Function
Storing
Retrieved
Rows in
Two
Dimensional
Array
Logical Operations
Arithmetic Operations
Aggregate
Functions
Mathematical
Functions
Where
Clause
Single & Composite
PK
Query
LIMIT
Executing Query
Fig. 2. EETPS overview architecture
Fig. 3. The EETPS three database models
example
business requirements. In this example, we assume that the service provider has three
tenants. The
rst user has evaluated the Sales database and found that this database suits
his business requirements without any modi
cations. Therefore, this user will use the
Sales database schema as originally provided by the service provider as illustrated in
Fig.
3
(a). The second user has evaluated the Sales database schema and found that he
needs to add extra tables to ful
ll his business needs. Thus, this user created VET 1,
VET 2, and VET 3, and then, created virtual database relationships between these VETs
and the existing physical tables (CTTs) in the sales database schema. The database
model for this user is shown in Fig.
3
(b). The third user has evaluated the same database
schema and found that it did not suit his business requirements, and decided not to
use the Sales database schema at all, and instead created virtual relational tables from
scratch and established database relationships between them as shown in Fig.
3
(c).
When these three users have created and con
gured their database structures, they can
retrieve data from their databases by calling functions from EETPS. This example
illustrates the three database models that EETPS and EET schema provide. Using these
database models, users can design their databases and automatically con
gure their
behaviors during runtime. For more details about how to manage EET, we refer the
reader to [
24
].
Search WWH ::
Custom Search