IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


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.

Add a new idea Subscribe
Status Not under consideration
Workspace IBM Rational Business Developer
Categories EGL Language
Created by Guest
Created on Sep 24, 2008

RELATED IDEAS

Optimzing EGL pagination for large tables

EGL data table (UI) component supports in-memory pagination which requires all records to be fetched in an EGL array beforehand, and then paginates over that array. If a table has millions of records, all of them can not be fetched in one array and the application hangs.

In memory pagination, in principle, is not a recommended design. It turns out fatal with enterprise data running into millions of records.

We propose an optimized pagination feature wherein, records for only one page can be fetched at a time from database. Subsequently as user requests other page, records for that page can be fetched.

DB2 supports this kind of pagination, and the approach is described in online DB2 documentation.

SQL query depends on business requirements. But it can be generalized by parameterizing its parts e.g. SELECT clause, FROM clause, WHERE clause, etc can be specified by applications and EGL runtime can put them together to prepare the pagination query.

Idea priority High
  • Guest
    Reply
    |     Sep 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - Business Developer

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Business Developer

  • Guest
    Reply
    |     Apr 16, 2009

    We agree that this would be a desireable enhancement. However, it is unlikely to be prioritized for implementation in the near to mid-term timeframe. We may revisit this requirement in future planning cycles.

  • Guest
    Reply
    |     Oct 16, 2008

    We agree that this would be a desireable enhancement, and would increase the power / productivity of the EGL language. It will be considered for implementation in a future release.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.