You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While #1582 implements basic visualization support for the databases, it only allows to fetch a limited numbers of rows from the database. It however does not allow lazily loading more rows.
To implement that feature it must be possible to add an OFFSET to the query (apart from LIMIT).
Value
The IDE can implement the fully featured lazy visualizations.
Specification
Research what guarantees OFFSET gives us in SQL.
Is it deterministic enough in most implementations to be used for the use-case (lazily loading visualizations) we need? If not, we may need to materialize the whole query and have laziness only within sending data from the in-memory dataframe.
Implement code-gen for OFFSET.
Add slice operation and others to Database.Table.
Update the visualization preprocessor to support the offset.
Acceptance Criteria & Test Cases
The OFFSET codegeneration and materialization is tested.
The text was updated successfully, but these errors were encountered:
Summary
While #1582 implements basic visualization support for the databases, it only allows to fetch a limited numbers of rows from the database. It however does not allow lazily loading more rows.
To implement that feature it must be possible to add an OFFSET to the query (apart from LIMIT).
Value
Specification
slice
operation and others to Database.Table.Acceptance Criteria & Test Cases
The text was updated successfully, but these errors were encountered: