Re: OVERLOAD matching: varchar(10) & varchar(20)

[Justin Taylor <jtaylor.0ab@xxxxxxxxx>]

The OVERLOAD points to diff procedures, and those procedures have the query
details.  OVERLOAD IMO obfuscates the functionality, which I don't like.
But it can work.



On Mon, Feb 2, 2026 at 10:40 AM Daniel Gross <daniel@xxxxxxxx> wrote:

> Oh - and you are trying to detect the field/column for the WHERE clause
> out of the length of the parameter field?
>
> Not a good idea IMHO.
>
> Make it 2 parameters with OPTION(*NOPASS:*OMIT). If the user wants the
> original procedure with SERIAL#
>
>    procedure(serial_field);
>
> If the ORDER# is wanted:
>
>    procedure(*omit:orderno_field);
>
> And the user can even supply both fields if needed).
>
> This way you can detect it via %PASSED(...) and there are no ambiguities.
>
> HTH
> Daniel