|
https://www.ibm.com/support/pages/node/7169071
The cursor name that is generated for returning the result set of any SQL
table function has always been named SQL_TABLE_CURSOR. This namingapproach
can cause a cursor name collision when multiple SQL table functions are
used within a query. To circumvent a cursor name collision, the FENCED
clause must be used on the SQL table function. However, the FENCED clause
adds overhead to the execution of the table function by forcing it to run
in separate thread.
With this enhancement, the generated cursor name has been modified so itif
contains the table function name and the table function's library name,
the library name is available. This does not guarantee uniqueness, but
significantly reduces the possibility of a cursor name collision which
increases the likelihood that the NOT FENCED setting can be used.
Table functions must be rebuilt to pick up this change.
HTH,
Charles
On Tue, Oct 8, 2024 at 1:04 PM Darren Strong <darren@xxxxxxxxx> wrote:
The only thing that caught my interest was a passing mention of UDTFdoes
performance and unfenced. I already create unfenced UDTF's, so, what
this new thing do? Quoted as follows:Rob
"SQL User Define Table Functions (UDTFs) by providing the option to
generate unfenced NOT.FENCED code, improving performance"
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Berendtsubscribe,
Sent: Tuesday, October 8, 2024 9:14 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx
Subject: IBM i 7.5 TR5 and IBM i 7.4 TR11 announcements
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.
IBM i 7.5TR5
https://www.ibm.com/docs/en/announcements/i-75-tr5
https://www.ibm.com/support/pages/ibm-i-75-tr5-enhancements
IBM i 7.4TR11
https://www.ibm.com/docs/en/announcements/i-74-tr11
https://www.ibm.com/support/pages/ibm-i-74-tr11-enhancements
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
unsubscribe, or change list options,list
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
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.