Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable dynamic browse of table contents #3557

Open
audiomuze opened this issue Aug 21, 2019 · 5 comments

Comments

@audiomuze
Copy link

commented Aug 21, 2019

Details

EDIT by Pawel: This issue will track progress on "dynamically loading/expanding data rows", while #3558 was created to track issue of incorrect number of pages.

Original post:

I find sqlitestudio is great for exploring data in a table and in-flight editing when data issues are identified. The one thing I find very frustrating though is that sqlitestudio only loads the first 833 rows in the default view and the only way I can see to access other records is to browse query results, which again only shows the first 833 results. I've got Number of Rows per page set to "99999" - which is the maximum the configuration dialog will allow. Despite this, I can only see the first 833 rows in the table I've open. Is there a way to view/browse/edit data beyond these first 833 rows in order to be able to explore the entire table without having to resort to queries to browse subsets of the data? This is particularly useful when one is browsing the table to get a feel for the data/ contents with a view to enhancing through update queries, especially where the data is not generated from an app e.g. from populating a table based on metadata collected from files in a filesystem where the contents may be a little less predictable.

Screenshot from 2019-08-21 09-01-03

Screenshot from 2019-08-21 09-00-12

@pawelsalawa

This comment has been minimized.

Copy link
Owner

commented Aug 21, 2019

Well, how do you know there is more than 833 rows? Because it seems like you have 833 rows. Otherwise you would see remaining rows.

Setting the limit to such big number as you did is not a good idea. You may exhaust your computer's memory. Keeping it between 1000-5000 sounds reasonable. You always can browse pages (there are buttons with arrows to switch between pages).

Still, even by default you have 1000 rows per page, so if you have more than 833, you would see 1000.

@audiomuze

This comment has been minimized.

Copy link
Author

commented Aug 21, 2019

Hi

Thanks for the feedback re config. I must be missing something obvious on my end:

Screenshot from 2019-08-21 09-50-01

The table has 180 fields, which seems to be the reason only 833 records are shown in a page. Nevertheless, according to sqlitstudio there are only 5 pages available - that gets me as far as 4165 records.

Screenshot from 2019-08-21 09-55-28

No idea why sqlitestudio assumes only 5 pages?

Also, would it not be possible to implement dynamic browsing whereby up/down/pgup/pgdn loads elements of the next/previous page depending on where the cursor is at?

@pawelsalawa

This comment has been minimized.

Copy link
Owner

commented Aug 21, 2019

Dynamic loading is rather big change. We can keep this report to track this feature implementation.

Anyway, regarding your problem, there may be a bug for case when you have so many columns. Maybe number of pages is not calculated correctly in this case. Let's try this - limit rows per page (in config) to 500 and then see how it behaves, whether you can reach last records.

@audiomuze

This comment has been minimized.

Copy link
Author

commented Aug 21, 2019

I'd just done that prior to your last posting. There is a bug when the limit is set too high. I changed the limit to 5000 rows and that solved the ability to browse all records - pages changed to 545 and all records are now accessible.

Screenshot from 2019-08-21 10-06-09

Thanks for the feedback and responsiveness by the way, really appreciate it.

@pawelsalawa

This comment has been minimized.

Copy link
Owner

commented Aug 21, 2019

Okay, I will update your original post at the top to include both the bug and the enhancement proposal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.