×
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.
"LEON" never appears in the script, so I have no idea where SQL is
getting it, other than it being the user profile under which the script
is being run.
James,
That is exactly the point. As the constraint name wasn't qualified, SQL
inserted the user name as a default qualifier (ie., schema) name. So, when
your developer wrote:
ALTER TABLE "RB_DBO"."RB_ACTION" ADD CONSTRAINT "PK_RB_ACTION" PRIMARY KEY
("ACTION_ID");
The system changed it to:
ALTER TABLE "RB_DBO"."RB_ACTION" ADD CONSTRAINT "LEON"."PK_RB_ACTION"
PRIMARY KEY
("ACTION_ID");
Just use the same qualifier in the constraint name:
ALTER TABLE "RB_DBO"."RB_ACTION" ADD CONSTRAINT "RB_DBO"."PK_RB_ACTION"
PRIMARY KEY
("ACTION_ID");
Best Regards,
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
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.
midrange.com
