Display Name: Give your data source a name for use within Internal.
Endpoint: EXAMPLE: cluster.us-east-1.redshift.amazonaws.com:5439/dev
Username: Credentials for this data source.
Password: Credentials for this data source.
To connect with Internal, your data source must be publicly accessible, with SSL encryption enabled, and configured to accept connections from Internal’s IP addresses.
When you connect Redshift to Internal, we'll generate the following for you automatically:
- A list, insert, update, and delete function for each table in the database (if the connecting user account has these privileges). List functions read data from your tables and allow you to display that data in components - think of these as prebuilt SQL queries, so you don't have to write queries for everything.
Functions will not be generated if no primary keys are found in the connected database.
While Internal enables filtering and sorting on all columns, we recommend indexing columns on large tables to improve performance.
Internal requires SELECT permissions in the pg_catalog schema in order to load your database schema information. We currently use the following tables:
Read about building a Redshift CRUD App on our blog.
Updated 11 months ago