![]() ![]() ![]() |
![]() |
|
|
![]() ![]() ![]() ![]() ![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Return to Views Views play an important role as a means to structure information with respect to specific users' needs. While read access through views is easy to handle, update requests through views are difficult in the sense that they have to be translated into appropriate updates on database relations. In this paper the constant complement translator approach towards view updating proposed by Bancilhon and Spyratos is revisited within the realm of SQL databases, and a novel characterization is established showing that constant complement translators exist precisely if users have a chance to undo all effects of their view updates using further view updates. Based on this characterization view updates with and without constant complement translators are presented. As it turns out that users cannot fully understand updates on views violating the constant complement principle, the application of this principle in the context of external schema design is discussed. @inproceedings {DBLP:conf/pods/Lechtenborger03, author = {Jens Lechtenbörger}, booktitle = {PODS}, title = {The impact of the constant complement approach towards view updating.}, pages = {49-55}, year = {2003}, url = {db/conf/pods/pods2003.html#Lechtenborger03}, ee = {http://doi.acm.org/10.1145/773153.773159}, crossref = {conf/pods/2003}, bibsource = {DBLP, http://dblp.uni-trier.de} } ![]() ©2004 Association for Computing Machinery |