Why the relational data model can be considered as a formal basis for group operations in object-oriented systems
| dc.creator | Grigoriev, Evgeniy | |
| dc.date | 2007-08-02 | |
| dc.date | 2007-09-05 | |
| dc.date.accessioned | 2026-07-07T08:27:23Z | |
| dc.date.available | 2026-07-07T08:27:23Z | |
| dc.description | Relational data model defines a specification of a type "relation". However, its simplicity does not mean that the system implementing this model must operate with structures having the same simplicity. We consider two principles allowing create a system which combines object-oriented paradigm (OOP) and relational data model (RDM) in one framework. The first principle -- "complex data in encapsulated domains" -- is well known from The Third Manifesto by Date and Darwen. The second principle --"data complexity in names"-- is the basis for a system where data are described as complex objects and uniquely represented as a set of relations. Names of these relations and names of their attributes are combinations of names entered in specifications of the complex objects. Below, we consider the main properties of such a system. | |
| dc.description | 10 pages | |
| dc.identifier | https://arxiv.org/abs/0708.0361 | |
| dc.identifier | http://arxiv.org/abs/0708.0361 | |
| dc.identifier.uri | http://salesiana.dossiersoluciones.com/handle/123456789/137256 | |
| dc.subject | Databases | |
| dc.subject | E.2; D.3.3; F.3.3; F.4.1; H.2.1; H.2.3; H.2.4; H.3.3 | |
| dc.title | Why the relational data model can be considered as a formal basis for group operations in object-oriented systems | |
| dc.type | text |