An SQLO front-end for Relational Databases with Non-Monotonic Inheritance and De-referencing
By Hasan Jamil and Joel Oduro-Afriyie
*My comments start with an asterisk
He presented the motivation of the work, claiming that despite some progress, this is still an unsolved issues. He motivated his work also by the opinions of other developers on blogs and forums.
The idea is to keep using SQL and also enabling the use of objects and whatever else the developer wants.
He shows some possible commands for which he proposes some modifications. And then, he exemplifies what happens in a table hierarchy having several levels of abstract tables. He basically shows what properties are or are not inherited among the tables, depending on redefinitions and the general inheritance properties.
He showed a slide with an ERRATA, correcting some typos in the paper.
He gave some examples of queries generated from their proposed specifications. An important note is that all his queries are in instance level, so "instance view (iv)" is constantly used in his queries.
*This is a nice paper if you are teaching SQL, because it has a lot of examples of SQL operations and their results.
Q&A
Vítor: What is the benefit of doing this directly on SQL and not on OO languages that already implement this in a higher-level? He responded that the only reason why languages have done that is that this was not possible in SQL, so they had to work around it. But he is trying to provide these choices so as to make the programming part more simple.
By Hasan Jamil and Joel Oduro-Afriyie
*My comments start with an asterisk
He presented the motivation of the work, claiming that despite some progress, this is still an unsolved issues. He motivated his work also by the opinions of other developers on blogs and forums.
The idea is to keep using SQL and also enabling the use of objects and whatever else the developer wants.
He shows some possible commands for which he proposes some modifications. And then, he exemplifies what happens in a table hierarchy having several levels of abstract tables. He basically shows what properties are or are not inherited among the tables, depending on redefinitions and the general inheritance properties.
He showed a slide with an ERRATA, correcting some typos in the paper.
He gave some examples of queries generated from their proposed specifications. An important note is that all his queries are in instance level, so "instance view (iv)" is constantly used in his queries.
He showed some of his previous works that have served as foundation, and that have been extended.
Q&A
Vítor: What is the benefit of doing this directly on SQL and not on OO languages that already implement this in a higher-level? He responded that the only reason why languages have done that is that this was not possible in SQL, so they had to work around it. But he is trying to provide these choices so as to make the programming part more simple.
Nenhum comentário:
Postar um comentário