The only thing a MySQL integration needs is a live MySQL server the user has access to, and a set of credentials. Concretely, the required arguments are:
Although there is no limitation regarding the chosen database server (any MySQL server will work, provided it is configured appropriately in the previous section), there is a limitation in the data types that our platform can work with. The list of supported data types is:
Note: Columns of other types, more complex ones, are not supported and will silently be ignored on data synchronization.
Two modes are supported: "Key Based" / "Incremental", and "Full Table".
"Full Table" completely wipes out any data in our platform the stream previously downloaded, and then the whole data from the stream's source table is dumped into our platform. This mode is not recommended for big tables.
"Key Based" (also called "Incremental") requires a particular field to be selected as "key". That field is meant to be treated as a sequential or "sortable" field which increases by time (i.e. records added in the future will have never descending values in this field), and will be tracked across several extraction executions from the (same) integration's stream.
The first run, the whole table data will be downloaded into our platform, and the maximum value for that tracked key (i.e. the one from the last record retrieved) is kept for future runs. This will be time-consuming (as time-consuming as Full Table replication, but done only once) and the source servers may undergo a lot of resources consumption, so these runs should be scheduled on what the customer deems as low-activity hourly ranges (e.g. nightly).
When another extraction is run later for this incremental stream, only a subset of the data will be retrieved: Those having values, in the chosen key-field, greater than or equal to the last stored value.
As an example: Let's say the source table contains "sold product units", containing these fields: