This portal is to open public enhancement requests against products and services offered by the IBM Data & AI 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 updateson 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
Just recently while working on a customer we were able to speedup a very slow query by using the recently introduced OLAP functions.
The query looks like this:
SELECT col1, col2, col3, col4, rank() over (partition by col1, col2 order by col4 desc) myrank FROM some_table WHERE col5=1
But we just want the record where col4 = (SELECT MAX(col4) FROM some_table b WHERE b.col1 = some_table.col1 AND b.col2 = some_table.col2) Basically we want the records where col4 is higher in groups defined by col1,col2. To introduce this filter we should be able to use an "HAVING myrank = 1", but this raises error -217 (column myrank not found).
The current solution is to do an inline view with the above query and use the filter "myrank = 1" in the outside query:
SELECT col1, col2, col3, col4 FROM ( SELECT col1, col2, col3, col4, rank() over (partition by col1, col2 order by col4 desc) myrank FROM some_table WHERE col5=1 ) WHERE myrank = 1
But this seems a bit awkward and I have some doubts about the performance (will it need to materialize the inline view and then scan it again?). We introduced the ability to use column alias in GROUP BY clause, but apparently this was not extended to the HAVING clause. That's the purpose of this RFE
Do not place IBM confidential, company confidential, or personal information into any field.