NetNews Usenet Archive 1992 #30/NN_1992_30.iso/spool/comp/database/ingres/2105

Internet Message Format | 1992-12-16 | 3.4 KB

Path: sparky!uunet!europa.asd.contel.com!emory!sol.ctr.columbia.edu!ira.uka.de!gmd.de!jvnc.net!badboy.protocol.zycad.com!dominick
From: [e-mail] (Dom Paniscotti)
Newsgroups: comp.databases.ingres
Subject: Re: Windows 4GL vs. ESQL interfaces
Date: 16 Dec 1992 10:12:56 -0500
Organization: Protocol, a Division of ZYCAD Corporation
Lines: 51
Sender: [e-mail]
Distribution: world
Message-ID: <[e-mail]>
References: <kitchel.724345020@manta> <[e-mail]> <[e-mail]> <[e-mail]> <[e-mail]>
Reply-To: [e-mail]
NNTP-Posting-Host: hayaku.protocol.zycad.com
Keywords: ESQL, Windows 4GL, database interface.


In article <[e-mail]>, [e-mail] (William Thompson, code 682.1, x2040) writes:
|> In article <[e-mail]>, [e-mail] writes...
|>
|>     (stuff deleted)
|>
|> >I may be true that Inges Windows/4GL is tied (heavily) to the GUI, but for
|> >someone who needs to rapidly develop an X based database application it's
|> >probably the best way to go.  I've also found it to be a good way to
|> >rapid prototype an application (you get functional windows very quickly).
|> >However, given enough time and money, I would have to say I would develop
|> >my application using ESQL/C and and a good GUI development package.  I think
|> >(IMHO) the later would produce a much more maintainable application
|> >than one written in W4gl.
|>
|> You start by saying how good W4GL is, and then you say you'd rather not use it.
|> Could you expand on why you end up with that conclusion?
|>
|> Bill Thompson

Like I said, "given enough time and money" -- Which is something this
software engineer never has enough of :-).  I'll give you a real life
example.  I recently was asked to develop an X-based configuration
management application, my initial estimate was >2 man years (using
ESQL and XbuilderAccessory (sp? -- a GUI development tool)).  I was
told that there was only enough funding for 1 man year.  I went back
and decided to re-bid the job using the 4GL.  My new estimate ending
up being just over 1 man year.  The final product ending up being
developed on time and budget using the 4GL. BTW, that was using W4GL
ver 1.x (no 4GL debugger, and lots of core dumps).
-- So much for the testimonial --
If I would have had the 2 man years however, I would have developed using
ESQL and C for a few reasons:
    1.  There are more people who know SQL and "C" -- therefore, it easier
            to maintain the code down the line. Furthermore, I'm not stuck
        with it since "He's the 4GL guru" :-).
    2.  You can design much more flexible GUI's using a GUI development
        tool (Ingres supports a fixed set of widgets and doesn't let
        you design custom ones.
    3.  The 4GL is not as powerful/flexible/etc. as "C"
    4.  You are now tied to Ingres.  You could have possibly ported
        the SQL and "C" code. (What happens if Ingres decided to close
        shop or drop the W4GL product; unlikely, but...)

    Hope this clears things up,
        Dom
--
Dom Paniscotti                  internet: [e-mail]
Protocol, a Division of ZYCAD   phone:    [phone]
500 International Drive         fax:      [phone]
Mt. Olive, NJ 07828