Documentation

Write to MySQL

To write data to MySQL with Flux:

  1. Import the sql package.

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

    • driverName: mysql
    • 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 (default is 10000)
import "sql"

data
    |> sql.to(
        driverName: "mysql",
        dataSourceName: "user:password@tcp(localhost:3306)/db",
        table: "example_table",
    )

MySQL data source name

The mysql driver uses the following data source name (DSN) syntax (also known as a connection string):

username:password@tcp(localhost:3306)/dbname?param=value

Flux to MySQL data type conversion

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

Flux data type MySQL data type
float FLOAT
int BIGINT
uint BIGINT
string TEXT(16383)
bool BOOL (TINYINT)
time DATETIME

MySQL BOOL types

BOOL is a synonym supplied by MySQL for convenience. MySQL stores BOOL values as TINYINT types so looking at the schema shows the column type as TINYINT.


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: