Abstract: Systems and methods are described for using secondary mappings in an Object Relational Mapping (ORM) system to enable source code changes to be implemented and carried out without requiring updates to the database schema. In order to use secondary mappings, one or more attributes of an object in the ORM system are annotated to indicate that they are secondary mapped attributes. The annotation can indicate to the ORM system that the various operations (e.g. read operations, write operations) referencing attributes of the object may need to be remapped if the column for the attribute being referenced does not actually exist in the database. For example, if no column is directly mapped to the attribute being referenced, the ORM system can remap the operation to point to a secondary data structure (e.g. a map stored in-memory) that will be used to store the value for that attribute.

Abstract: Systems and methods are described for using secondary mappings in an Object Relational Mapping (ORM) system to enable source code changes to be implemented and carried out without requiring updates to the database schema. In order to use secondary mappings, one or more attributes of an object in the ORM system are annotated to indicate that they are secondary mapped attributes. The annotation can indicate to the ORM system that the various operations (e.g. read operations, write operations) referencing attributes of the object may need to be remapped if the column for the attribute being referenced does not actually exist in the database. For example, if no column is directly mapped to the attribute being referenced, the ORM system can remap the operation to point to a secondary data structure (e.g. a map stored in-memory) that will be used to store the value for that attribute.