Closed fosron closed 2 years ago
I think having an option to not save (or clear existing) result/inferred schema would be more than enough. That way project does not hold too much data.
Thank you for the report! It would also help if you could send me a .dsproj file that has this issue.
When I upgrade myself it normally works for me so it's concerning you've been having issues upgrading!
It's not about the upgrade, i'm creating new projects, they all do act the same after some time. As for sending a .dsproj, i need to come up with something that has no personal data and fails.
Ok I'm going to introduce a workaround where it will not error out if the shape becomes bad. Hopefully that will allow you to re-run and fill it with a valid shape.
I can't solve the actual issue until I see an example dsproj if you can send one, since I've never had this for me (though you've clearly demonstrated it does happen).
Just an update on the underlying issue, all the data is driven by the UI at the moment and stored in JSON on disk in a single giant blob.
I'm splitting this out to be more reliable/sane, also moving to store all project data (not the results data) in SQLite. That should be out next month and should deal with the many subtle storage bugs there are right now.
Sounds great, thanks!
Hey,
so it's seems that after returning to an already existing project im getting this error (for every panel, im using TimescaleDB via SSH, PostgreSQL via SSH, Code SQL and Table outputs)
The only remedy i found is to copy everything to a new project, not even new tabs work. I guess this is has something to do with how existing data is stored.
Also there's this in
Table
type:Datastation v0.7.0 MacOS 12.2.1 (21D62) Intel Mac (MacBook Pro (13-inch, 2019, Four Thunderbolt 3 ports))