We do all of our "classic" database IO access through logical files with one logical file unique to each application. Each logical file only has the fields that the application needs to use. So added a new field anywhere in the physical has no impact on any application because the application does not even know it exists until you also change the logical file used by that application.
SQL SELECT access to the database doesn’t care about the sequence of fields in the physical
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Friday, February 24, 2017 3:29 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Storing source as DDL instead of DDS
Do the DBAs question you when you say you want to name the column Z010_My_Column_name? :-) Or have you managed to explain the Z010 prefix with a straight face?
The the next column is Z020_This_Column
:-)
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: dlclark@xxxxxxxxxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 02/24/2017 03:22 PM
Subject: RE: Storing source as DDL instead of DDS
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 02/24/2017
03:12:04 PM:
For those storing the source. How do you deal with the addition of
new fields (columns)? Since you have to use ALTER TABLE to add a
column, the source for adding a field to an existing file is
completely different from the original creation of the field at file
creation time. Do you save the original CREATE TABLE and all
subsequent ALTER TABLE commands in the script so you can recreate
the table if needed?
We store the source because we use change management. The DBA's
are also struggling with how they want to manage ALTERs, etc. The last I
heard they were going to store the ALTER's (in an SQLALTSRC source
physical file) and update the original CREATE (in an SQLTBLSRC source
physical file), too. I don't know where they are with it now.
But, there is also the issue of where do you add new columns to
existing tables. As programmers we are pushing for only adding new
columns to the end of the definition so that existing programs are
impacted as little as possible. The DBA's wanted to add them in
alphabetical order to keep things "nice" and "clean." <<shudder>>
Sincerely,
Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331
*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.
*********************************************************************************************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
________________________________
This email may contain confidential information about a Pennsylvania College of Technology student. It is intended solely for the use of the recipient. This email may contain information that is considered an “educational record” subject to the protections of the Family Educational Rights and Privacy Act Regulations. The regulations may be found at 34 C.F.R. Part 99 for your reference. The recipient may only use or disclose the information in accordance with the requirements of the Federal Educational Rights and Privacy Act Regulations. If you have received this transmission in error, please notify the sender immediately and permanently delete the email.
midrange.com
