Core data updating records
From that point on the author's code manipulates these Core Data objects, rather than the underlying v Cards.
Connecting the menu item to the appropriate method in the controller object will direct the controller to examine the object stack, determine which objects are dirty, and then re-write a Core Data document file with these changes.
Throughout its history, EOF contained a number of bits of useful code that were not otherwise available under Ne XTSTEP/Open Step.
For instance, EOF required the ability to track which objects were dirty so the system could later write them out.
Unlike EOF, it is not possible to write your own SQL, as the underlying store may not be SQL-based.
Recently, Core Data store for ODBC has been made available in ODBC framework. If you have the Xcode Data Model file, you can read and write files in that format freely.
EOF was an object-relational mapping for high-end SQL database engines such as Microsoft SQL Server and Oracle.
The EOF object model was deliberately designed to make the resulting programs work in a document-like fashion; the user could edit the data locally in memory, and then write out all changes with a single Save command.This was presented to the developer not only as a document-like system, but also in the form of an unlimited Undo command stack, with each command applied to the data represented as an undoable action.Many developers complained that this state management code was far too useful to be isolated in EOF, and it was later moved into the Cocoa API during the transition to Mac OS X. EOF was used primarily along with another Open Step-era product, Web Objects, which was an application server originally based on Objective-C.It allows data organized by the relational entity–attribute model to be serialized into XML, binary, or SQLite stores.The data can be manipulated using higher level objects representing entities and their relationships.