Re: Stored Procedure: Default Values For Parameters -- MIDRANGE-L

Subject: Re: Stored Procedure: Default Values For Parameters
From: rob@xxxxxxxxx
Date: Fri, 30 May 2008 11:55:49 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

SQL procedures support "overloading". So it's quite possible to create
the same procedure name, in the same library, with different parameters.
After all, it's not like you do a WRKOBJ MYLIB/MYPROC *SQLPROC and see an
object name that can't be the same for that object type or anything. The
procedure only exists in SYSPROCS

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Stored Procedure: Default Values For Parameters , Elvis Budimlic

This mailing list archive is Copyright 1997-2025 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.