## 13 EOModel class

### 13.1 overview

A model represents GDL2s interface to a database. It contains information required to connect to the database along with entities and stored procedures.

All the model classes can be written to and read from property list files in the form of .eomodel or .eomodeld files. While .eomodel files contain a model and all its entities and objects in a single property list, .eomodeld files are a directory with each of the property lists in their own file.

Typically you won’t create an model through manual instantiation of the classes but store them in and read them from a property list. We have provided an example .eomodel file See Example model file.

An EOModel Typically has:

1. A Name
2. An adaptor name
3. A connection dictionary
4. An array of entities