What happens if you attempt to add an attribute that violates the schema of an existing Entity?

When you attempt to add an attribute that violates the schema of an existing Entity in OutSystems, the operation will generate an error. This is because the schema defines the structure of the Entity, including the types and constraints of the attributes it allows. OutSystems enforces the integrity of the database schema, ensuring that any modifications adhere to these predefined rules.

If you attempt to introduce an attribute that does not comply with the existing schema, such as a data type mismatch or a violation of constraints like uniqueness or non-nullability, the system will reject the operation. This provides a safeguard against inconsistencies in the data model, ensuring that the database maintains its integrity and reliability.

The other options imply outcomes that do not reflect the strict nature of schema enforcement. For instance, the idea that the operation might succeed or that only some attributes may be added suggests a level of leniency that does not exist in this context. Similarly, the concept of automatic adjustments would undermine the system's design, as it is crucial for developers to explicitly manage schema changes to maintain clear control over the data structure.