You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to use libSQL (https://github.com/tursodatabase/libsql) as an adapter. Locally, I will use a sqlite file, and then, in production, I will use something like Turso.
Explain what kind of feature would support this
Adding a new adapter for libsql or adding infrastructure to support 3rd party adapters (If that exiosts already, please kindly point me to the docs or an example :) )
Give some API proposal, how the feature should work
Similarly to better-sqlite3, simple define libsql as the adapter.
I would love to contribute to the poject either by:
Building a libsql adapter and creating a PR to contribute it back to knex
Helping to act as a tester for an API that allows 3rd party adapters.
The text was updated successfully, but these errors were encountered:
One thing I'm noticing so far is that there are documentation-esque comments in the code that are not doc comments. For example, in client.js:
// The base client provides the general structure// for a dialect specific client object.classClientextendsEventEmitter{
Also, I'm wondering how it will work to build a dialect in pure typescript. There are type definitions for the external APIs, but not for the client code, AFAICT. Turns out there are type definitions for the Client API 👍🏼
Environment
Knex version: N/A
Database + version: libsql
OS: N/A
Feature discussion / request
I would like to use libSQL (https://github.com/tursodatabase/libsql) as an adapter. Locally, I will use a sqlite file, and then, in production, I will use something like Turso.
Adding a new adapter for libsql or adding infrastructure to support 3rd party adapters (If that exiosts already, please kindly point me to the docs or an example :) )
Similarly to
better-sqlite3
, simple definelibsql
as the adapter.I would love to contribute to the poject either by:
The text was updated successfully, but these errors were encountered: