{"title":"关系DBMS的语言抽象层","authors":"N. Stanger","doi":"10.1109/SEEP.1996.533986","DOIUrl":null,"url":null,"abstract":"Current database definition techniques tend to be either purely language based or purely graphical. There is little or no integration between the two. This places artificial limits on the environment that developers must work in; ideally, they should be able to switch paradigms as the need arises. This lack of integration also causes problems with database reengineering. The paper describes an architecture for a relational abstraction layer, which isolates the front end \"dialect\" used from the underlying relational implementation. This allows tighter integration between different database definition techniques.","PeriodicalId":416862,"journal":{"name":"Proceedings 1996 International Conference Software Engineering: Education and Practice","volume":"15 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1996-01-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"A language abstraction layer for relational DBMS\",\"authors\":\"N. Stanger\",\"doi\":\"10.1109/SEEP.1996.533986\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Current database definition techniques tend to be either purely language based or purely graphical. There is little or no integration between the two. This places artificial limits on the environment that developers must work in; ideally, they should be able to switch paradigms as the need arises. This lack of integration also causes problems with database reengineering. The paper describes an architecture for a relational abstraction layer, which isolates the front end \\\"dialect\\\" used from the underlying relational implementation. This allows tighter integration between different database definition techniques.\",\"PeriodicalId\":416862,\"journal\":{\"name\":\"Proceedings 1996 International Conference Software Engineering: Education and Practice\",\"volume\":\"15 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1996-01-24\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings 1996 International Conference Software Engineering: Education and Practice\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/SEEP.1996.533986\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings 1996 International Conference Software Engineering: Education and Practice","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SEEP.1996.533986","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Current database definition techniques tend to be either purely language based or purely graphical. There is little or no integration between the two. This places artificial limits on the environment that developers must work in; ideally, they should be able to switch paradigms as the need arises. This lack of integration also causes problems with database reengineering. The paper describes an architecture for a relational abstraction layer, which isolates the front end "dialect" used from the underlying relational implementation. This allows tighter integration between different database definition techniques.