|
On Thu, Aug 5, 2021 at 7:30 AM Niels Liisberg <nli@xxxxxxxxxxxxxxxxx>
wrote:
statements
Select LongNewName as OLDNAME from my table ...
Yes - It will work, however I can not change all our clients SQL
and it will lead to maintenance of each column name twice. Perhaps this
will be the solution for now, if I can not find a real solution to the
issue. But I will not be a hero in the eyes of the guys that have to go
through all the code. Perhaps they will even prefer to go back to DDS :(
Please don't take this with any disrespect. I'm just curious, and I
don't fully understand the situation. What benefit were you trying to
gain by moving away from DDS?
Also, would it be possible to automate the code modifications?
John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
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.