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