DuckDB 1.0 is now available!
We can now move forward on these topics!! ![]()
Cool, it might arrive in time for the development of the improved graphics!
Edit: typo
Hi everyone,
Is this thread still relevant following the switch to DuckDB? ![]()
If not, we can close it ![]()
Even if the DB size issue is resolved, it wasnât the main topic discussed here (even if it was one of the repeated arguments).
For my part, it remains incomprehensible to store « useless » data while knowing that you can do otherwise.
But with the « updated_at » column having now disappeared in DuckDB (
) it no longer makes much sense because it was the best way to ensure the proper receipt of the data.
In any case, from what we can see so far, the performance is there with DuckDB so itâs no longer a primary concern for me.
Iâll let you decide what you do with it ^^
Ok, Iâll close it then. That wonât prevent re-creating a topic if thereâs a real need in the future.
For me, simplicity is a real feature, and if we can do without this functionality, that suits me.