Skip to main content
Feedback

SQL Deprecated connector

warning

This connector is now in Deprecated status. It is no longer available for new users and is not actively maintained. We will provide a minimum six-month notice before its retirement. We recommend upgrading to the newer supported version of this connector.

The SQL Deprecated connector allows you to read and write data from an SQL database.

The SQL Deprecated connector provides a way of loading, saving and deleting data in your flows using an SQL database. For example, you may wish to integrate an existing database into your Flow to display and work with database table data.

The SQL Deprecated connector currently supports the following SQL database types:

  • MySQL

  • PostgreSQL

  • SQL Server

During the connector installation your database metadata will be read and each table and view will be mapped to a Flow Type. You can then use a Load step in your Flow to read and display rows from the database tables, and the Save and Delete steps to modify rows in the tables.

For example, you can load rows from a database table into a page in your Flow to display, and then allow a user to edit the rows and save their results back to the database, as shown in the example below.

example table using SQL database

  • In the example image above, the SQL connector is being used with a Load step to read data from an SQL database into a page in a Flow. Individual rows in the table can then be edited and saved back to the database using a Save step.

Connector URL

The SQL connector endpoint URL is:

Features

The SQL Deprecated connector forms part of the following features within Flow:

  • Database: This connector feature allows you to connect to a remote data source and perform save, load and delete operations.

Known limitations

  • The SQL Deprecated connector requires a table to have a Primary Key and AutoIncrement defined. Only standard tables with primary keys are supported by the connector. If a database is used where the primary key is not supported, in views the connector will use all the columns in the table as a primary key.

  • There is a limit of 1000 returned rows for each database query; if a query load is requested with a size bigger then the max supported size will be used. The maximum number of steps that can be executed in a row without a break (i.e. a step or page) is 1000.

  • There is a 100 second maximum duration for connector invoker calls. After this duration, the connector invoker call is cancelled.

  • Only PostgreSQL has support for changing the names of the Flow Types via the column descriptions.

  • The MONEY type is not supported when using the SQL Deprecated connector with an SQL Server database type.

  • Although a large variety of data types are supported, if the data type is not supported then the column will be ignored; if the column is not null in the table you will not be able to insert or save in the Flow. Refer to supported SQL data types.

  • When applying filters to date/time value columns in custom components, the value supplied must use the ISO-8601 extended offset date-time format in order for the connector to correctly parse the value. For example

    2011-12-03T10:15:30+01:00

    To learn more about this date/time format, refer to the ISO_OFFSET_DATE_TIME API specification. Refer to Formatting date and time values to learn more about formatting date/time values in Flow.

On this Page