Need to refresh page to update Mosaic plot - non-deterministic behavior about mosaic HOT 2 CLOSED

I believe the issue stems from the fact that your specs create a table with the same name. By default, the data loaders will not replace an existing table, so when you navigate from one page to another without reloading, the DuckDB-WASM instance persists, including any previously loaded tables. This would explain both the binder error and why re-loading resolves the issue.

So I think there are multiple solutions you could apply...

1. If you want to replace any existing table with the same name, update your data definition to specify this:

data:
  charges: { file: data/EIN_74110155_houston-methodist-hospital.parquet, replace: true }

2. Or, if you always use distinct table names, your app will load all the various tables and keep them loaded (until the page is reloaded).

3. Alternatively, you could update your web application logic to first drop all tables when navigating to a new page, basically performing a "hard reset" of the DuckDB-WASM instance.

For simplicity (and to prevent the number of loaded data tables from getting too large), I would probably default to option 1 above -- assuming this does not interfere with other Mosaic specs loaded on the same page.

from mosaic.

Got it, thank you so much @jheer! That makes sense, will give it a shot 🙏

from mosaic.