Re: Changing database to SQL from DDS

[rob@xxxxxxxxx]

The problem is the Joe Palooka who comes in after you will only look at 
the DDS and compile that.  I suppose you try something like never naming 
your DDS the same as your file.  But they still wouldn't "seek first to 
understand".  They would curse your parents, rename it, and continue.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




Mlpolutta@aol.com
Sent by: midrange-l-bounces@midrange.com
01/08/2003 05:41 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     midrange-l@midrange.com (Midrange Systems Technical 
Discussion)
        cc: 
        Fax to: 
        Subject:        Re: Changing database to SQL from DDS


If you're using a "script" to create your database via SQL, then I would 
think that a combination of DDS definitions and CL commands in a CL 
program (script) would be equivalent.  I don't see much more than a 
semantic difference between the MAKE file and the script.

Michael Polutta

> The problem to that is recreating the databases.  Granted CHGPF is nice 
> because you don't lose the constraints.  But to create one from scratch 
> you have to create a MAKE tool to rebuild a file, if you 
> use DDS.  In SQL, 
> this can all be contained in the script.
> 
> Rob Berendt


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.