Send data to MySQL / MariaDB¶

GeoJibe can write the result of a workflow straight into a MySQL or MariaDB table.

GeoJSON Transform MySQL / MariaDB

You need to be signed in. Download is not involved — MySQL / MariaDB is the Destination.

MySQL / MariaDB appears only when GeoJibe's GDAL runtime includes the MySQL driver.

This writes one spatial table. It is not a schema, stored-procedure, or user migration.

Before you start¶

You'll need:

Save the connection once, then reuse it.

Open Destinations → Add Destination → MySQL / MariaDB.

Fill in Host, Port, Database, Username, and Password.

Click Test, then Save. Name it something like Production GIS.

The saved Destination is the database login. Table and write mode belong to each workflow.

Upload or import a vector dataset. Add Transform or Convert if you need them.

MySQL / MariaDB is for vector data.

If you used Convert to reproject, MySQL / MariaDB receives that CRS. GeoJibe does not reproject again at the Destination.

Add MySQL / MariaDB and select the saved Destination.

Then set:

Field	Typical value
Table	`neighborhoods`
Write mode	See below

Mode	What it does
Create	Creates a new table. Fails if the table already exists.
Replace	Overwrites the table if it exists.
Append	Adds rows to an existing table. Fails if the table is missing.

Warning

Replace mode can overwrite an existing destination table.

Click Run, or Send to MySQL / MariaDB in Classic.

You should see a successful delivery to the table.

GeoJibe writes the converted layer into that table (geometry column geom, InnoDB). Open it in QGIS or your database tool to confirm.

This is a one-off unless you save a Job.

Example: GeoJSON → MySQL / MariaDB.