Comments on the debate: data-structure-set versus relational

J. Clymer
{"title":"Comments on the debate: data-structure-set versus relational","authors":"J. Clymer","doi":"10.1145/984403.984406","DOIUrl":null,"url":null,"abstract":"In the belief that it might be worthwhile for someone to attempt a summary of the \"Great Debate,\" I have tried to set down my own observations and wlll pass them on to you for whatever they may be worth. Suppose we consider that there wlll be three supported interfaces to future data base systems, and describe these suggestively as an End User Interface, an Application Programmer Interface, and a Systems Programmer Interface. Table 1 shows how these might very roughly be characterized. (Note: By systems programmer I am referring to the data base management system and not to the operating system.) There seems to be little argument that the End User Interface should have a basically relational view, or that some form of network view will be required for the Systems Programmer Interface. This is because the concept of independence from logical data structure more or less implies the relational view for the higher level~, and the requirement to eliminate redundancy from the stored data more or less implies a network view for the lower level. I gather, then that the central thrust of the debate is over what form the Application Programmer Interface should take. This does seem to be a substantive issue, and not merely a \"religious\" argument. Dr. Codd's position seems to be that the application programmer should be able to request data In relational terms and have it supplied by the data management facility into his work area, where he may then operate upon it in. whatever fashion he wishes; or that he be able to call upon the data management facility to take data from his work area described in relational terms and store it into the data base. To the extent that the data base contains linkages and indices required to reduce redundancy and improve efficiency, it will be the responsibility of the data management facility to manage these, and they should be essentially invisible to the application programmer. In this way the viewpoint of the application programmer and the end user will be essentially the same, and communication between them will be easy. The task of the application programmer will be reduced and he will make fewer mistakes because he will not have to be concerned with how he acquires the data he wants to manipulate, but only with its specification.","PeriodicalId":123835,"journal":{"name":"FDT Bull. ACM SIGFIDET SIGMOD","volume":"7 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1975-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"FDT Bull. ACM SIGFIDET SIGMOD","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/984403.984406","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 1

Abstract

In the belief that it might be worthwhile for someone to attempt a summary of the "Great Debate," I have tried to set down my own observations and wlll pass them on to you for whatever they may be worth. Suppose we consider that there wlll be three supported interfaces to future data base systems, and describe these suggestively as an End User Interface, an Application Programmer Interface, and a Systems Programmer Interface. Table 1 shows how these might very roughly be characterized. (Note: By systems programmer I am referring to the data base management system and not to the operating system.) There seems to be little argument that the End User Interface should have a basically relational view, or that some form of network view will be required for the Systems Programmer Interface. This is because the concept of independence from logical data structure more or less implies the relational view for the higher level~, and the requirement to eliminate redundancy from the stored data more or less implies a network view for the lower level. I gather, then that the central thrust of the debate is over what form the Application Programmer Interface should take. This does seem to be a substantive issue, and not merely a "religious" argument. Dr. Codd's position seems to be that the application programmer should be able to request data In relational terms and have it supplied by the data management facility into his work area, where he may then operate upon it in. whatever fashion he wishes; or that he be able to call upon the data management facility to take data from his work area described in relational terms and store it into the data base. To the extent that the data base contains linkages and indices required to reduce redundancy and improve efficiency, it will be the responsibility of the data management facility to manage these, and they should be essentially invisible to the application programmer. In this way the viewpoint of the application programmer and the end user will be essentially the same, and communication between them will be easy. The task of the application programmer will be reduced and he will make fewer mistakes because he will not have to be concerned with how he acquires the data he wants to manipulate, but only with its specification.
关于争论的评论:数据结构集与关系
我相信有人对这场“伟大的辩论”做一个总结是值得的,我试着把我自己的观察记录下来,不管它们是否有价值,我将把它们传递给你们。假设我们认为未来的数据库系统将有三种受支持的接口,并将它们概括地描述为终端用户接口、应用程序程序员接口和系统程序员接口。表1显示了这些特性的大致特征。(注:我所说的系统程序员指的是数据库管理系统,而不是操作系统。)最终用户界面应该有一个基本的关系视图,或者系统程序员界面需要某种形式的网络视图,这似乎没有什么争议。这是因为独立于逻辑数据结构的概念或多或少意味着较高层次的关系视图,而从存储数据中消除冗余的需求或多或少意味着较低层次的网络视图。我认为,争论的中心焦点是应用程序程序员接口应该采取何种形式。这似乎是一个实质性的问题,而不仅仅是一个“宗教”的争论。Codd博士的立场似乎是,应用程序程序员应该能够以关系方式请求数据,并让数据管理设施将其提供到他的工作区域,然后他可以在那里对其进行操作。无论他喜欢什么式样;或者他能够调用数据管理工具,从用关系术语描述的工作区域中获取数据,并将其存储到数据库中。如果数据库包含减少冗余和提高效率所需的链接和索引,那么管理这些将是数据管理设施的责任,并且它们对应用程序编程人员基本上是不可见的。通过这种方式,应用程序程序员和最终用户的观点将在本质上是相同的,并且他们之间的通信将很容易。应用程序程序员的任务将会减少,他将会犯更少的错误,因为他将不必关心如何获取他想要操作的数据,而只需关注其规范。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:604180095
Book学术官方微信
小红书