If you try to open a database with Kexi, and a table has millions of entries, if you will put scroll bar at bottom down, you will not see lastest entry, but Kexi will be stuck at a certain entry of the table. In a few words: Kexi cannot scroll down after a certain data record Reproducible: Always
Thanks for the report, Germano What would be the minimum number of records that still demonstrates the issue?
(In reply to Jarosław Staniek from comment #1) > Thanks for the report, Germano > > What would be the minimum number of records that still demonstrates the > issue? Did you mean: "after how many records do you experience the bug"?
Yes, (at least): how many.
Lastest record I can partially see is number 932068
Thanks! Will be tested with 1M of records. By the way, out of curiosity, what db driver is that?
(In reply to Jarosław Staniek from comment #5) > Thanks! Will be tested with 1M of records. > > By the way, out of curiosity, what db driver is that? The original file is a MDB file.
Ah, so imported. Good.
Thanks, confirmed on a 2M of records.
Created attachment 94209 [details] For 2M of records, not even half of them visible.
For me ends at row 883011 no matter if there are 1M or 2M rows to show....
Found it: QWIDGETSIZE_MAX/row_height == 16777215/19 == 883011 I will have to employ some math to overcome the limit.
Example with 1M of records (1.3MB): http://kexi-project.org/download/tests/351702-1M.kexi.xz
Fixing it takes more time than expected. Looking for solutions.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
I am no longer able to import a MDB file so I cannot verify the status of the bug