× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



We don't have any reason to keep DDL source at all.
What happens if a DDL described database object gets lost, i.e. an Index or
a view or even worse an view based on multiple views gets deleted.
What if a trigger or constraint is deleted?

How will you recreate it, if the object does no longer exist, so reverse
engineering is no longer possible?

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Justin Taylor
Sent: Freitag, 24. Februar 2017 20:25
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Storing source as DDL instead of DDS

I agree. All our new PF's are DDL, but we're not going out of our way to
replace existing DDS PF's.

IF you have a compelling reason to store DDL source, keeping it with your
DDS source makes the most sense to me. We don't have any reason to keep DDL
source at all.



-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Friday, February 24, 2017 12:28 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Storing source as DDL instead of DDS

My thoughts on this.

Doing a wholesale migration from DDS to DDL has some benefits but I am not
certain it would be the best use of your companies money at this time.
Doing all new development using DDL instead of DDS is a reasonable approach.

Since you would be supporting a mixed environment one option would be to put
the DDL into the same QDDSSRC pf. While this may drive a purist mad I
believe it would make the transition for a new employee the easiest.
Hopefully, they would look for the DDS for the file, find the source member
and quickly realize that it's in DDL and they need to switch gears.
If they can't figure that out, you've made a hiring mistake.


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

--
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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.