EMBEDDED SQL: Optional values in where clause? -- RPG400-L

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

Subject: EMBEDDED SQL: Optional values in where clause?
From: "Thomas Gard" <thomas.gard@xxxxxxxxx>
Date: Tue, 18 Apr 2006 19:16:48 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

I believe recently I saw a thread here or somewhere on how to deal
with optional predicates in a where clause, i.e. sometime parms will
be passed in to be used in where clause, sometime not, its possible to
set the where clause to function accordingly on what is passed in.  I
cant recall where I saw it and did not bookmark it, can anyone point
me to the thread or highlight how to do that, thanks.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: EMBEDDED SQL: Optional values in where clause? , Michael_Schutte

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.