|
Mike, What type of procedure or trigger are you trying to define? Not sure about SQL procedures or triggers, but I would imagine it would default to a schema named the same as your user profile (sql naming) or QGPL (system naming) If your defining external RPG procedures I would recommend qualifying with the program name with the program or database library, but not qualifying the external program name, that way the system can search your library list for the program when you use system naming cheers Colin.W Extension 5800 Direct dial 0870 429 5800 -----Original Message----- From: Mike Pantzopoulos - (H/O) [mailto:mpantzopoulos@xxxxxxxxxxxxxxxx] Sent: 11 April 2005 08:17 To: midrange-l@xxxxxxxxxxxx Subject: Triggers and Procedures. I'm not sure if this is the right list for an SQL question but here goes. I can't find any documentation detailing where SQL creates a procedure or trigger when it's created without a specific library reference. It seems that QGPL is where the procedure is placed and the file (in the case of the trigger) it's placed on is the first file of that name encountered in the library list. I have versions of the code working with hard-coded library references on the procedure and file the trigger is buased on but am trying to avoid the hard-coding as we have a 3 tier release process and I'd like to be able to keep versions quite separate. I have the SQL Reference an SQL Programming Guide, but can't find any details concerning these topics. Mike Pantzopoulos EIG-Ansvar Limited Tel : 61 (3) 9614 3535 Fax: 61 (3) 9614 2740 **************************************************************************** ***************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, any use, disclosure or copying of this message is unauthorised. If you have received this message in error, please reply using the sender's email address. This footnote confirms that this email message has been scanned for computer viruses. EIG-Ansvar Limited does not accept liability for any loss or damage, whether caused by our own negligence or not, that results from a computer virus or defect in the transmission of this email or any attached file. EIG-Ansvar Limited - Australia (A.B.N. 21 007 216 506) Email : insure@xxxxxxxxxxxxxxxx Eig-Ansvar Limited - New Zealand Email : insure@xxxxxxxxxxxxxxxx **************************************************************************** ***************************** -- 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. This e-mail has been sent by a company of Bertram Group Ltd, whose registered office is 1 Broadland Business Park, Norwich, NR7 0WF. This message, and any attachments, are intended solely for the addressee and may contain privileged or confidential information. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you believe that you have received this email in error, please contact the sender immediately. Opinions, conclusions and statements of intent in this e-mail are those of the sender and will not bind a Bertram Group Ltd company unless confirmed in writing by a director independently of this message. Although we have taken steps to ensure that this email and any attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free.
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.