RE: sql continue handler -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: sql continue handler
From: Rob Berendt <rob@xxxxxxxxx>
Date: Wed, 24 Aug 2022 13:52:31 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

I've never had that situation.
I guess if you're determining something on the fly, like what library to create the procedure in, and then you're using that to create it, I guess.
But as far as host variables on WHERE or ORDER I'd find some way to pass those in as parameters to the stored procedure.

Rob Berendt

Follow-Ups:

Re: sql continue handler , Jay Vaughn

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