Object Registers

Constant Outrapreocupao is that, generally, the SGBDs, as well as many applications, has its closed code hindering an extended vision of what it occurs: umacaixa is black, where if of the one entered in agreement to the established standards paraaquela box, where the magician happens, and ' ' PLIM! ' ' , it is its result, prontopara there to be used. Not wanting to judge, therefore the creator always has right sobresua creation. To open the code or is not decision of it. CPU-Bound the PostGre temgrande to be able of processing. It is as, after Oracle, in processamentode complex and long consultations. Each consultation generates a transaction in the bank dedados, that goes since the analysis of the syntax in the application of the customer until the retornodos registers, and this transaction has distinct time of CPU for each SGBD.

Otempo and the resources that the PostGre consume are high, they resultadoscompensam but them. You could write a long sequncia of JOINs in the MySQL eiteraes between tables one children determined ID, what she would imply emvrias consultations, but in PostGre becomes it request of these emapenas registers a consultation that is returned in only some milliseconds. Guided Objects This aspectofoi, of far, what it surprised more me. Even before I knowing oPostGreSQL, in my academic life, already listened to rumors of dadosOrientados banks of the Object, but that still he was in development and that quaseningum used. He asked to me, frequently: – For that we have that to study Guided umLinguagem the Objects if when to use a bank pra we will dadosteremos to persist them to think again Structuralized? It was there that I knew the PostGre xD. Pretty Quedia was that one in the lesson the professor of the mini-course of 2 InfoUnir, emPorto Old, showed the possibility to decriar Schemas, a species of classroom and, inside of the classroom, it places itself tabelasrelacionadas.