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



>>Only if the short name and the alias name are *both* incorrect.

That means you can change the long_name but keep the short one and vice
versa.
Could you please explain how'd you do that, i.e. change the system name or
the SQL name for a column ?


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

-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von CRPence
Gesendet: Wednesday, 15.5 2013 16:23
An: rpg400-l@xxxxxxxxxxxx
Betreff: Re: change column name in sql?

On 14 May 2013 22:26, Birgitta Hauser wrote:
There is no way to alter a column name, neither the long SQL nor the
short system name.
What you can do is to add a new column with the desired name, data
type and length. (If there are already data within the old column copy
these data into the new column). And delete the old column after.

Only if the short name and the alias name are *both* incorrect.

A bit more complicated than just that for the scenario presented, wherein
one of the two names [short and alias] is correct, but the other is
incorrect. In that case, the "new column" can not be added, because one of
the two names for the new\corrected column would be a duplicate of the
correct name in the "old column". Introducing an additional set of add\drop
column ALTER requests using something like "add column bogus_alias_name for
bogus_name" would be required... and of course the additional corresponding
UPDATE if data were present. All the more reason to just DROP TABLE and
re-create might be better... separately dealing with dependencies, data,
ownership, and authority issues required for that action.

--
Regards, Chuck
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.