is different between server and static page.
- Server mode: Python/DuckDB reads the parquet natively and preserves row order when materializing pp_data. So LIMIT 10000 really does return the first 10k
rows in parquet order -- interleaving fixed it there.
- Static viewer: DuckDB-WASM with BROWSER_FILEREADER materializes the table but doesn't preserve parquet row order internally. So LIMIT 10000 returns rows
in DuckDB's internal storage order regardless of parquet layout -- interleaving had no effect.
Maybe we want to add specific columns that are always fully checked, or disable the limit in static view.
is different between server and static page.
rows in parquet order -- interleaving fixed it there.
in DuckDB's internal storage order regardless of parquet layout -- interleaving had no effect.
Maybe we want to add specific columns that are always fully checked, or disable the limit in static view.