resultset displaying issue about dbeaver

[ShadelessFox]

Hello @skriszo,

Try disabling this option:

[skriszo]

hi @ShadelessFox,
then I lose the possibility to fetch the records incrementally.
maybe it is a misunderstanding, but when I say "then DBeaver keeps fetching records endlessly", I mean that whenever I scroll down DBeaver fetches a new batch of records, but it never ends.
eg.: the table (or whatever I query from) contains only 25 rows, DBeaver does not stop at 25 (which would be the correct behaviour), but it fetches zillions of records.

[ShadelessFox]

I believe the RECURSIVE clause causes this. Try putting the LIMIT clause in the outer query.

[skriszo]

@ShadelessFox, this query was just for demonstrative purposes, it behaves like this with simple select * from table as well.
and also, I am not the one who puts the LIMIT clause anywhere, but DBeaver. This is what this setting is for:

[ShadelessFox]

Sorry, I can't reproduce this exact scenario.

By default, DBeaver fetches rows until the entire screen is filled with data. This can be turned off as demonstrated here: #29930 (comment)

To be able to fetch next pages of data, you might need to enable such an option here:

So that you can access it from the toolbar:

[skriszo]

well, according to my experience DBeaver fetches data until it reaches the record count that is set here (does not depend on window size):

yes, this Fetch Next Page equals with scrolling down with Auto-fetch next segment turned on and the issue appears with this as well.
However, I tried the same thing with an Oracle connection and it worked fine, so it is a Teradata related bug. Also what I noticed as a difference:

even with this setting turned on

with an Oracle connection the queries do not get extended with FETCH FIRST x ROWS ONLY (this is the oracle syntax for LIMIT)
while with a Teradata connection they do get extended with TOP x (Teradata syntax for LIMIT)