Introduction this paper will analyze the current situation of the databases (oodb) object-oriented and see why a system as traditional as the relational remains a strong letter to many of the developers of software and databases. The awareness that a developer must have different programming paradigms, must be necessary in a way that allows you to opt out of any of them, bearing in mind that many times the decision is due to the different needs of the system in question and still one of the most used the structured paradigm so far. Currently the object oriented programming has gained ground because that allows to solve the problem from a conceptual approach to take it to a model in which the elements comprising it are fragmented and classified according to certain similar characteristics, thus allowing a better management of the system. In the management and development of databases occurs something different, the relational databases (db), followed in force today and account for the largest percentage of sales in the market (database relational dbms engines). Developing a database is a collection of data that can be organized so that its contents can be accessed, managed and easily update 1. For any company the actions mentioned in the text above are of utmost importance, since currently all business information systems (I dare to mention a 95%) are based on this kind of computational data model. A relational database model is a set of relations (frequently called tables).
Each table in turn is a set of records, rows, or tuples. And each of these is a set of fields, columns or attributes 2. In a database object-oriented, information is represented by objects such as those present in the OOP 3. To make use of any type of bond is therefore necessary a manager of databases that would be responsible for all operations structural and data update.