Modeling: User's Guide

Previous: 3.3.5 Misc. Up: 1 The essentials Next: 4.1 Ensuring unicity of

---

 
4. Working with your objects: insert, changes, deletion

Now that we have seen how an object interacts with the core, we still have to learn about how they can be inserted, updated or deleted and how these changes can be made persistent into a RDBMS.

There is one component which fulfills these goals: the EditingContext. EditingContext can be thought as a graph of objects. Its major feature is to hold objects at runtime for which it is its responsability to track changes, either in the object (changes for some of an object's attributes) or between objects (when the objects in relationships change).

Everything you do within an EditingContext is likely to be made persistent (given that the objects derive from CustomObject and that they have a corresponding entity defined in some model).

• 4.1 Ensuring unicity of an object
• 4.2 Inserting an object
• 4.3 Updating objects
• 4.4 Deleting an object
• 4.5 Fetching objects
  • 4.5.1 Principles
  • 4.5.2 Simple fetch
  • 4.5.3 Pattern matching
  • 4.5.4 Equality, comparisons, in and not in
  • 4.5.5 Negating, Con- or disjoining qualifiers
  • 4.5.6 Dotted notation
  • 4.5.7 How much objects will a query fetch?
  • 4.5.8 Fetching and inheritance
  • 4.5.9 The influence of an EditingContext on fetchs
  • 4.5.10 Fetching raw rows
    • 4.5.10.1 Getting raw data
    • 4.5.10.2 Turning rows into real objects
• 4.6 Saving Changes
• 4.7 Discarding changes: the destruction process of an EditingContext
  • 4.7.1 Finalizing an EditingContext: breaking reference cycles
  • 4.7.2 Controlling the finalization stage

---

Modeling: User's Guide

Previous: 3.3.5 Misc. Up: 1 The essentials Next: 4.1 Ensuring unicity of

---

Release 0.9, documentation updated on March 4, 2006.

Comments are welcome: Sebastien Bigaret / Modeling Home Page
Hosted by: