Browsing Russian translation

240.

The object 'tiny.object' inherits from all the columns and all the methods from the n objects 'tiny.object_a', ..., 'tiny.object_n'.

241.

To inherit from multiple tables, the technique consists in adding one column to the table tiny_object per inherited object. This column will store a foreign key (an id from another table). The values *'name_col_a' 'name_col_b' ... 'name_col_n'* are of type string and determine the title of the columns in which the foreign keys from 'tiny.object_a', ..., 'tiny.object_n' are stored.

242.

This inheritance mechanism is usually called " *instance inheritance* " or " *value inheritance* ". A resource (instance) has the VALUES of its parents.

243.

Module development

244.

OpenERP uses a `three-tier architecture <http://en.wikipedia.org/wiki/Multitier_architecture#Three-tier_architecture>`_. The application tier itself is written as a core and multiple additional modules that can be installed or not to create a particular configuration of OpenERP.

245.

The core of OpenERP and its different modules are written in `Python <http://python.org/>`_. The functionality of a module is exposed through XML-RPC (and/or NET-RPC depending on the server's configuration). Modules also typically make use of OpenERP ORM to persist their data in a relational database (PostgreSQL). Modules can insert data in the database during installation by providing XML (or CSV or YML) files.

246.

Although modules are a simple way to structure a complex application, OpenERP modules also extend the system. Modules are also called addons (they could also have been called plugins).

247.

In a typical configuration of OpenERP, the following modules can be found:

248.

base: the most basic module; it is always installed and can be thought as being part of the core of OpenERP. It defines ``ir.property``, ``res.company``, ``res.request``, ``res.currency``, ``res.users``, ``res.partner``, and so on.

249.

crm: Customer & Supplier Relationship management.