Open thetutlage opened 3 months ago
Here's a reproduction https://github.com/thetutlage/knex-turso-example
Just as an aside, I had better luck connecting with wss://
over libsql://
Just as an aside, I had better luck connecting with
wss://
overlibsql://
how your connection got established
I have this problem too. I tried playing with the pool config but didn't work. The config looks like this:
knex({
client: Client_Libsql,
connection: { filename: "<URL>" },
pool: { min: 0, idleTimeoutMillis: 1000, reapIntervalMillis: 100 },
})
Similar to the issues reported in Python lib https://github.com/tursodatabase/libsql-experimental-python/issues/41 and Go lib https://github.com/tursodatabase/libsql/issues/985
I am also getting the same error when using LibSQL with Knex. I see this PR that resets the connection when resource is released to the pool for the Go implementation https://github.com/tursodatabase/libsql/pull/1100. Do we have to do something similar?