What is the incorrect mapping between OutSystems entities and standard database components?

The mapping of OutSystems entities to standard database components is generally straightforward and logical. Entities in OutSystems correspond to tables in a traditional database structure, meaning each entity represents a record set within the application. Attributes, which are defined within these entities, correspond to the columns in a database table, as they hold the data for each entity instance.

When it comes to reference attributes, it's crucial to clarify their role. A reference attribute in OutSystems is used to establish a connection to another entity, effectively creating a foreign key relationship in the database. However, not all reference attributes are synonymous with primary keys. Primary keys uniquely identify records within their table, while reference attributes merely point to those records in another table. Thus, stating that a reference attribute is a primary key is incorrect as it overlooks the distinct function of reference attributes.

Understanding these mappings is essential for effectively using OutSystems and relational databases. Recognizing that each component has its specific role helps to avoid confusion regarding how data is structured and interrelated within the system.