The Hierarchy of data at a Dbquity Site

Using the In app, a number of published site models may be deployed to a Dbquity site.

As prescribed by the Dbquity Metamodel, each deployment creates a number of areas at the site; one for each area declared, and inside each area, a number of entity collections, associations and containers will appear and be populated by nested entities forming a hierarchy of entities as the site is used; all according to the declarations of the deployed models. An area can only exist at the top level of the site hierarchy, and other types of entities always reside inside an area.

For example, the ShoppingList example model

creates this hierarchy at deployment:

• area Setup
  • collection Units
  • collection Items
• area Shopping
  • collection Lists
  • collection ToBuy

which during actual use will fill up with entity instances, e.g., like this:

• area Setup
  • collection Units
    Unit "liter"
    Unit "kg"
    Unit "6-pack"
    Unit "pcs"
    ...
  • collection Items
    Item "milk"
    Item "potatoes"
    Item "bread"
    ...
• area Shopping
  • collection Lists
    List "1"
    List "2"
    ...
  • collection ToBuy
    ToBuy List "1" x Item "milk"
    ToBuy List "1" x Item "potatoes"
    ToBuy List "2" x Item "bread"
    ...

Note that an association is implemented as a collection of entities that each associate individual entities.