Managing Object Persistence During OOM to CDM Generation

Developers tend to use object-oriented programming languages like Java, to develop business objects and components. Eventually, these objects can be represented in a conceptual data model prior to being stored in a database. A problem arises because object codes in object-oriented programming languages are often different than codes used in a CDM.

You can define persistent codes to bypass this impedance-mismatch.

• Defining Object Persistence in the OOM
  Persistent codes are codes defined for OOM classes and attributes that are used during OOM to CDM generation. They also facilitate round-trip engineering by allowing you to recover object codes from the conceptual data model.
• Managing Complex Data Type Persistence
  In the following example, both classes are defined as persistent.
• Managing Multiplicity for Complex Persistent Data Types
  If you define a multiplicity on a class attribute with a complex data type, the generation will reflect this multiplicity.

---

Created October 7, 2009. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com