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

Why does prepare require you to iterate through the result set?

On Mon, Dec 4, 2017 at 1:24 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

I'm working off the documentation here:

The Basic Query example works fine and returns the entire result set as a
JS object. That's all well and good until I need to insert user-input into
the WHERE clause. I can't just poke raw user-input into the SQL
statement. It looks like I can do parameters with a prepared statement,
but that requires me to iterate thru the result set (rather than returning
all at once).

Do I need to use a prepared statement and manually reconstruct the result
set, or is there a better way?


This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/opensource.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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