Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Data Explorer: Always read fresh file contents when ingesting a file …
…into duckdb (#5890) Addresses #5860. duckdb-wasm has some kind of file caching behavior that is not resilient to file changes on the underlying file system. This patch nukes this issue from orbit by always registering the file contents as a virtual file and reading from that. I think if and when we migrate to the duckdb NodeJS bindings per #5889 that we can avoid this chicanery. This does the same thing for Parquet files, too, since they would also become stale. e2e: @:data-explorer ### QA Notes Here was the reproducible failure from the issue: * Run iris |> readr::write_csv("test.csv") * Click on the file in the File Explorer to open it up; note that we correctly see the iris data * Run mtcars |> readr::write_csv("test.csv") * Again click on the file in the File Explorer to open it up; note that we incorrectly still see the iris data
- Loading branch information