Repository navigation
fix(linux): seek paging, lazy tab restore, grid speed, narrow bottom bar - #3468
Merged
Merged
Conversation
A table with no key walks PostgreSQL heap block windows, so no page sorts the whole table. OFFSET stays under a user sort. An unsorted export of such a table no longer orders by ctid.
A new page measures from scratch, a draft measures nothing, and the digits' width is laid out once per width, font and text scale.
The cell shapes all the text it is given though one line shows, and the tooltip quotes 300 characters.
Every bind of every cell scanned all pending edits for its row's state and copied its pending value, only to pick a class.
Discard also clears the undo history, so nothing brought the changes back. The browse and structure tabs now confirm it, as F5 already does.
The Rows dropdown offered only its five sizes, so a tab reading 2,500 rows showed 1,000, and picking 1,000 did nothing. It now lists the tab's own size too.
The tab is a breakpoint bin of its own: below 680sp Export, Filter, Count Rows and the page size move into a More menu, the pager label ellipsizes, and the filter strip's buttons wrap. The floor test now measures an open table tab.
A restore opened and selected every saved tab, so each started its reads at once on a 4-connection pool, and those waiting past 5 s failed. Saved tabs now open unselected and read once they stay on screen.
A filter the server cannot take now stays on the stale banner over the rows, or on the error page, until a read lands. Count Rows under it shows the reason on its Try Again button.
The pager said "No rows on this page" for an empty table too.
Signed-off-by: Dat Ngo Quoc <datlechin@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
read_pagepages past the edge row's key (AfterKey/BeforeKey) and readsLastbackward from the end. A PostgreSQL table with no key walks heap block windows that double when short, so no read sorts the whole table. OFFSET stays under a user sort, a restored deep offset and a partitioned keyless table.ORDER BY ctid.Tid Range ScanorIndex Scan Backwardplan with noSeq ScanorSort.AdwBreakpointBin: below 680sp, Export, Filter, Count Rows and Rows per Page move into a More menu, and the bar fits the 360 px floor.last_page_waits_for_an_exact_total,discard_restores_without_phantom_ops, and two that asserted filter-error toasts.