|
On Aug 23, 2018, at 4:36 PM, Mike Jones <mike.jones.sysdev@xxxxxxxxx> wrote:
Hi Chris,
That depends on what you want to do with the data.
In general, if you can avoid a cursor, you should. For example, if all you
want to do is log the result set produced by the PARSE_STATEMENT UDF, you
may be able to do something like:
insert into MY_PARSED_SQL_LOG_TABLE
select * from table( PARSE_STATEMENT() )
Mike
On Thu, Aug 23, 2018 at 10:16 AM Chris Holko <christopherholko@xxxxxxxxx>
wrote:
I want to use qsys2.parse_statement within my SQLRPGLE program but I am--
curious if the only option is to use it within a declare cursor/fetch
construct?
The routine is part of an ODBC exit hanging off of QIBM_QZDA_SQL2. It can
return more than one row per SQL statement passed.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
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.