Google Cloud SQL Non-Spatial Reader/Writer

FME can read and write attribute data stored in a Google Cloud SQL database. There are two versions of this reader and writer:

  • Google Cloud SQL Non-Spatial, which is an attribute-only version that ignores geometry
  • Google Cloud SQL Spatial, which includes the spatial extension and supports geometry features

This reader/writer communicates directly with the MySQL C API interface for maximum throughput.

This chapter assumes familiarity with Google Cloud SQL, the table types, column types, available server daemons, indexing mechanisms and connection parameters.

Note  This format is based on the MariaDB/SkySQL (MySQL-compatible) Non-Spatial Reader/Writer. It uses terminology specific to MySQL, since MariaDB is known to work well with MySQL Servers.

Google Cloud SQL Non-Spatial Product and System Requirements

Format

FME Platform

Operating System

Reader/Writer

FME Form

FME Flow

FME Flow Hosted

Windows 64-bit

Linux

Mac

Reader

Yes

Yes

Yes

Yes

Yes

Yes

Writer

Yes

Yes

Yes

Yes

Yes

Yes

Reader Overview

FME considers a reader dataset to be a database containing a collection of relational tables, and a table to be an FME feature type with each row corresponding to at least one FME feature.

Tables schemas must be defined in the FME workspace before they can be read.

Arbitrary WHERE clauses and joins are fully supported, as well as an entire arbitrary SQL SELECT statement. The basic reading process involves opening a connection to the database, querying metadata, and querying data. The data is read by submitting SQL queries and parsing the returned result sets.

Writer Overview

The MySQL writer module stores both geometry and attributes into an MySQL database, and has the following capabilities:

  • Transaction Support: The Google Cloud SQL Non-Spatial writer provides transaction support that eases the data loading process. Occasionally, a data load operation terminates prematurely due to data difficulties. The transaction support provides a mechanism for reloading corrected data without data loss or duplication. Performance can also be improved by reducing transactional overhead for multiple small queries such as inserts.
  • Index Creation: The Google Cloud SQL Non-Spatial writer can set up and populate indexes as part of the loading process. By default, no indexes are created. Columns can be individually indexed. Composite column indexes are not supported at this time.
  • Insert Binding: By default, the Google Cloud SQL Non-Spatial writer uses prepared statements and query parameter binding ensure speedy data loading.