Documentation

Write to SQLite

To write data to SQLite with Flux:

  1. Import the sql package.

  2. Pipe-forward data into sql.to() and provide the following parameters:

    • driverName: sqlite3
    • dataSourceName: See data source name
    • table: Table to write to
    • batchSize: Number of parameters or columns that can be queued within each call to Exec (set to 999 or less)
import "sql"

data
    |> sql.to(
        driverName: "sqlite3",
        dataSourceName: "file:/path/to/example.db?cache=shared&mode=ro",
        table: "example_table",
    )

Requires file system access

To query SQLite, Flux must have access to the filesystem. If Flux does not have access to the file system, the query will return an error similar to one of the following:

  • Error: unable to open database file
  • failed to read file: filesystem service is uninitialized
  • An internal error has occurred

If using InfluxDB Cloud or InfluxDB OSS, the Flux process does not have access to the filesystem.


SQLite data source name

The sqlite3 driver uses the following DSN syntax (also known as a connection string):

file:/path/to/example.db?param=value

Flux to SQLite data type conversion

sql.to() converts Flux data types to SQLite data types.

Flux data type SQLite data type
float FLOAT
int INT
uint INT
string TEXT
time DATETIME

Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: