I know I'll probably get blasted for saying this. But I must admit that
I've never been a big fan of using SQL to create tables. I understand that
using SQL will allow me to create table with feature that is not supported
by DDS (such as Identity column). But that is IBM's fault not mine :).
The main reason I didn't like SQL is because it strains my eye to read that
SQL create table statement. DDS is just much neater and easier to read.
"Brian Piotrowski" <bpiotrowski@xxxxxxxxxxxxxxx> wrote in message
news:mailman.26577.1296584617.2702.midrange-l@xxxxxxxxxxxx...
Hi All,
For years (prior to my arrival), the programs written around here were all
based on physical file definitions. However, these definitions were never
really consistent - a field of one type may not be the same type and length
in another file. We then began moving to creating tables with SQL
statements, keeping in mind the importance of creating fields that were the
same type and length regardless of the table in which they were used.
However, this was cumbersome because we always had to keep a running list of
field definitions along with their sizes and types.
We're now looking to move back to physical file definitions with a twist -
all definitions will be contained in a single dictionary file that lists all
of the fields, their types and their lengths. Even though we will have to
do a lot of data table conversion, I am hoping this will allow us to
centralize the definitions and not have to worry that a field in one table
may not be the same in another.
Has anyone had any experience similar to our current conundrum and if so,
did you solve it using a similar method? If not, what worked best for you?
Thanks!
/b;
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Assistant Mgr. - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x343
Fx: 705-435-5029
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
http://www.simcoeparts.com
Please consider the environment. Don't print this e-mail unless you really
need to.
The information contained in this communication is confidential and intended
only for the use of those to whom it is addressed. If you have received
this communication in error, please notify me by telephone (collect if
necessary) and delete or destroy any copies of it. Thank you!
midrange.com
