Original sentence: An alternate solution might be to use a truely relational DBMS.Because SQL doesn't implement relational separation of the physical and logical levels, it can be very expensive to submit several queries in a row.Early fully-relational implementations such as Ingres QUEL and IBM BS/12 never gained traction, and only recently a new RDBMS has appeared, Alphora Dataphor.Given these two very different worlds, object code for working with databases tends to be complex and susceptible to bugs.SQL, despite its deficiencies, is generally capable of a much faster global performance than OO.The ideal solution would be to use an object database, which, as the name implies, is a database designed specifically to look at and work with object programs.Unfortunately SQL, which doesn't fully implement the relational model, has long dominated the market and even academia
Edited sentence: Due to the failure of SQL to implement relational separation of the physical and logical levels, it can be very expensive to submit several queries in a row.Given these two very different worlds, object code for working with databases tends to be very complex and bug-ridden.Its original implementations such as Ingres QUEL and IBM BS/12 never gained traction, and only recently a new RDBMS has appeared, Alphora Dataphor.SQL, if deficient, is generally capable of a much faster global performance than OO.The ideal solution is a relational DBMS.The quick-and-dirty solution would be to use an object database, which, as the name implies, is a database designed specifically to look at and work with object programs.Unfortunately SQL has long dominated the market and even academia