Xref: utzoo comp.databases:2982 comp.software-eng:1775 Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!cwjcc!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!bg0l+ From: bg0l+@andrew.cmu.edu (Bruce E. Golightly) Newsgroups: comp.databases,comp.software-eng Subject: Re: 4GL and Application Prototyping in Databases Message-ID: Date: 17 Jul 89 17:47:59 GMT Organization: Carnegie Mellon, Pittsburgh, PA Lines: 17 I have to comment on this. We do LOTS of development work using Ingres. The applications we develop fall largely into two categories; batch oriented systems are written using embedded SQL, and interactive systems are written using ABF. The amount of time devoted to the development process is not excessive, especially for the ABF based work. The only times we have experienced the kinds of things described is when we had problems getting the design frozen. Trying to write applications when the design is still a moving target gets REALLY frustrating. For those systems/applications where the design has stabalized, we have seen significant gains in productivity by using OSL and VIFRED. I will admit that there are occassions when it is necessary to drop into embedded C within an ABF application. As a rule, this is rare. I have only had to do this when I needed to perform some more complex operaitons than OSL would readily permit. Bruce