Client libraries for the following languages are available to query a Turso database:
The client libraries allow you to execute a single SQL statement, execute a batch of statements in an implied transaction, and perform an interactive transaction. The information that follows is common to all clients.
The client libraries require two pieces of information for initialization.
1. Database URL
You must have a libSQL database URL that identifies the logical database or
instance to connect with. You can get this using the Turso CLI by running
turso db list or
turso db show.
2. Authentication token
You must have an authentication token that authorizes your client application to
access the database. It should be a long-live token with no expiration. You can
get an auth token this using the Turso CLI by running
turso db tokens create
$DBNAME --expiration none.
With the libSQL client library, a batch is one or more SQL statements executed in order in an implicit transaction. The transaction is controlled by the libSQL backend. If all of the statements are successful, the transaction is committed. If any of the statements fail, the entire transaction is rolled back and no changes are made.
Interactive transactions allow you to execute a series of read and write statements in the context of a SQLite transaction. Reads and writes are all consistent within the scope of that transaction, unaffected by other client activity. The transaction API requires you to choose when to commit or roll back the transaction.
Interactive transactions are not supported when using a stateless HTTP-based client. They require a websocket-based client or local SQLite files.
Interactive transactions effectively lock the entire database for writing when a write is first performed, and until the transaction is committed or rolled back. libSQL aborts transactions after a 5 second timeout. Transactions may negatively impact overall database performance when used on high latency connections or with busy databases.