IBM Data Platform Ideas Portal for Customers
This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
Hello @Marcus Boone
Currently, users are unable to add query optimization prefixes like
LOCKING ROW FOR ACCESSbefore aSELECTstatement. This limitation prevents the fine-tuning of queries to improve performance in environments where many users are concurrently reading from the same table. The absence of this option can lead to unnecessary lock contention, slowing down query execution and impacting overall system performance.Example:
SELECT
customer_name,
order_date
FROM
customer_orders
FOR READ ONLY WITH LOCKING ROW FOR ACCESS
WHERE
customer_id = 123;
The enhancement would do:
This prefix tells the database to run the query with a "read-only lock" that does not block other users from performing write operations. The query gets its data, and other users can continue their work without interruption.
The enhancement would provide a way for users to add this kind of prefix (or select it from a menu of options) before their
SELECTstatement to optimize its behavior.Closing due to lack of feedback. If this is still valid and can help clarify, please advise and we can reopen.
Pradeep - can you please provide more context as to the use case and what the outcome is you are trying to achieve. It is preferred to prescribing a solution.