Many RDBMS brands support views, a virtual table that is essentially a stored query. Your database administrator might have set up views to:
Combine (JOIN) columns from multiple tables into a single virtual table that can be queried
Partition a large table into multiple virtual tables
Aggregate and perform calculations on raw data
Simplify data enrichment
It is common practice to constrain staff users to accessing only views in their database connection credentials.
Corticon's Enterprise Data Connector supports mapping a Vocabulary to an RDBMS view.
Using Associations
When Corticon Entities are mapped to View tables that were created without any WHERE clause in the Select statement (in other words, Corticon filters are NOT applied), Associations (in a View table) are not required as the Entities mapped to the View tables with no Join Expressions in the Vocabulary returns the expected results that include the Association.
Note: When Entities are mapped to View tables that were created with a WHERE clause in the Select statement (in other words, Corticon filters are applied), results are incorrect: Associations are required even when there is a View table for the Join Expressions. Attempts to map the View tables to the Entities in the Vocabulary will generate validation warnings for lost Join Expressions. A Join Expression currently cannot be mapped to its related View tables.
Combine (JOIN) columns from multiple tables into a single virtual table that can be queried