Closed fishmichael closed 4 years ago
Please try modify the poli.maximum-query-records in the poli.properties.
Sounds like the default value is a bit confusing for the init setup. I will consider to change the default value to unlimited.
Zhonglu,
That is perfect. I see the relevance of globally limiting the rows returned (some of our tables have 15 million rows).
For me I like to limit the rows returned in the query itself, however. Short of a dialog on the Query tab itself so that I could specify maximum rows per query (that would be great), I will just modify the SQL itself.
Thanks again for your prompt response!
Mike
On Fri, Jul 26, 2019 at 9:03 AM Zhonglu notifications@github.com wrote:
Please try modify the poli.maximum-query-records https://shzlw.github.io/poli/#/configuration?id=number-of-query-results in the poli.properties.
Sounds like the default value is a bit confusing for the init setup. I will consider to change the default value to unlimited.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/shzlw/poli/issues/27?email_source=notifications&email_token=ABEZSD2BIZELCHIAUN6EYWLQBLYZNA5CNFSM4IHDSHVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD24QN6A#issuecomment-515442424, or mute the thread https://github.com/notifications/unsubscribe-auth/ABEZSDZMHL4VMF7F3G6HAUDQBLYZNANCNFSM4IHDSHVA .
Zhonglu,
Created a couple of table components with queries against our DB2 database on the iSeries. Noticed that it is consistently only returning 1000 rows of data. I don't see anywhere to configure number of rows returned. Is this a hard-coded limitation?
Thanks,
Mike