Open ceckoslab opened 2 months ago
This is because new Session("./dir_for_table_already_exists")
create session in the same dir.
After create the new table testtable
you didn't call session.cleanup()
.
So, the second time you use the same dir as the session dir. testtable
already exists.
You can also avoid this by new Session()
which will create the session in random tmp dir.
I see @auxten
My intention is to have the inserted created tables & data available between sessions but I think that session.cleanup()
will wipe out all the data:
// Cleanup method to delete the temporary directory
cleanup() {
rmSync(this.path, { recursive: true }); // Replaced rmdirSync with rmSync
}
I suppose that my use case is a bit different ... probably the usual CHDB user often starts CHDB, queries directly some data structure (CSV, JSON ...) or inserts data in CHDB that is not required when a new session get's started.
Thanks, I understand. Currently, chDB session implementation is a little tricky. Like I explained here: https://github.com/orgs/chdb-io/discussions/196#discussioncomment-8406116 Here is the plan: https://github.com/chdb-io/chdb/issues/197#issuecomment-2327976725
I noticed that in the following conditions I get when I run the example script for second time:
Repro:
I usually create a new DB and use the new DB but not everyone would be doing the same and could reach the same problem.
System info:
Apple M2 Pro macOS 14.5 (23F79) Node v20.9.0