This community is for professionals and enthusiasts of the Genio platform.
Share your questions and challenges, and help your partners!


Rodrigo Serafim
On 8/23/19, 3:48 PM

Tables in Genio are not exactly the same thing as tables in a database, though for simple applications we may treat them as so.

However in complex relational models there is a need to refer to the same object in two different ways at the same time. The classic example is of a Flight between two Airports. If you have a table called AIRPO, and only than, then an ambiguity arises when you want to specify in the FLIGH table that you want a departure and an arrival airport.

These two entities "arrival" and "departure" are in fact what Genio does represent in its tables, hence in our documentation they are referred to as "Areas". They represent all the roles that a business object may fulfill.

Yet, they are references to the same physical table in the database. You do not have a list of all the departure airports and another list of arrival airports in the database. That would be redundant. You only have Airports. This is what "Domain" represents. The Domain is the shared physical table of two Areas.

So in this example, in Genio you would have three entries in the tables definitions:

Table name



Now you can unambiguously create two foreign keys in the Flights table, one pointing to Arrival and another pointing to Departure while keeping a single physical table named Airport in the database.

Keep Informed

About the Community

This platform is for beginners and experts willing to share their Genio knowledge. It's not a forum to discuss ideas, but a knowledge base of questions and their answers. Read Guidelines

Question tools

6 follower(s)


Asked: 8/20/19, 2:29 PM
Seen: 1195 times
Last updated: 9/26/19, 5:03 PM