In OutSystems, what determines how data is persisted in the database?

In OutSystems, data persistence in the database is primarily determined by Entity Diagrams, which define the structure of the entities (tables) as well as their respective attributes (columns) and relationships with one another. Entity Diagrams serve as a visual representation of the data model, illustrating how different entities are related and how data flows between them within the application.

By using Entity Diagrams, developers can specify not just the types of data that can be stored but also the constraints, references, and the organization of data in a way that ensures efficient and effective data management. This allows the underlying database to be structured appropriately to support the application’s requirements for data storage, retrieval, and integrity.

While data types, entity relations, and business logic are important components of the overall application architecture, they do not solely determine how the data is persisted in the database. Data types pertain to the kind of data stored within an entity but do not dictate the persistence structure itself. Entity relations describe how entities interact with one another, and business logic defines the rules governing the application's behavior. However, it is the Entity Diagrams that lay the groundwork for how that data is ultimately organized and stored.