Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →A PostgreSQL Interface for Drift Data
Use the Remoting features of the Drift JDBC Driver to create a PostgreSQL entry-point for data access.
There are a vast number of PostgreSQL clients available on the Internet. From standard Drivers to BI and Analytics tools, PostgreSQL is a popular interface for data access. Using our JDBC Drivers, you can now create PostgreSQL entry-points that you can connect to from any standard client.
To access Drift data as a PostgreSQL database, use the CData JDBC Driver for Drift and a JDBC foreign data wrapper (FDW). In this article, we compile the FDW, install it, and query Drift data from PostgreSQL Server.
Connect to Drift Data as a JDBC Data Source
To connect to Drift as a JDBC data source, you will need the following:
- Driver JAR path: The JAR is located in the lib subfolder of the installation directory.
Driver class:
cdata.jdbc.api.APIDriver
- JDBC URL:
The URL must start with "jdbc:api:" and can include any of the connection properties in name-value pairs separated with semicolons.
Start by setting the Profile connection property to the location of the Drift Profile on disk (e.g. C:\profiles\Drift.apip). Next, set the ProfileSettings connection property to the connection string for Drift (see below).
Drift API Profile Settings
Drift uses OAuth-based authentication.
You must first register an application here: https://dev.drift.com. Your app will be assigned a client ID and a client secret. Set these in your connection string via the OAuthClientId and OAuthClientSecret properties. More information on setting up an OAuth application can be found at https://devdocs.drift.com/docs/.
After setting the following options in the ProfileSettings connection property, you are ready to connect:
- AuthScheme: Set this to OAuth.
- OAuthClientId: Set this to the Client Id that is specified in your app settings.
- OAuthClientSecret: Set this to Client Secret that is specified in your app settings.
- CallbackURL: Set this to the Redirect URI you specified in your app settings.
- InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to manage the process to obtain the OAuthAccessToken.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Drift JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.api.jar
Fill in the connection properties and copy the connection string to the clipboard.
A typical JDBC URL is below:
jdbc:api:Profile=C:\profiles\Drift.apip;Authscheme=OAuth;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;CallbackUrl=your_callback_url;InitiateOAuth=GETANDREFRESH
Build the JDBC Foreign Data Wrapper
The Foreign Data Wrapper can be installed as an extension to PostgreSQL, without recompiling PostgreSQL. The jdbc2_fdw extension is used as an example (downloadable here).
- Add a symlink from the shared object for your version of the JRE to /usr/lib/libjvm.so. For example:
ln -s /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server/libjvm.so /usr/lib/libjvm.so
- Start the build:
make install USE_PGXS=1
Query Drift Data as a PostgreSQL Database
After you have installed the extension, follow the steps below to start executing queries to Drift data:
- Log into your database.
-
Load the extension for the database:
CREATE EXTENSION jdbc2_fdw;
-
Create a server object for Drift:
CREATE SERVER API FOREIGN DATA WRAPPER jdbc2_fdw OPTIONS ( drivername 'cdata.jdbc.api.APIDriver', url 'jdbc:api:Profile=C:\profiles\Drift.apip;Authscheme=OAuth;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;CallbackUrl=your_callback_url;InitiateOAuth=GETANDREFRESH', querytimeout '15', jarfile '/home/MyUser/CData/CData\ JDBC\ Driver\ for\ Salesforce MyDriverEdition/lib/cdata.jdbc.api.jar');
-
Create a user mapping for the username and password of a user known to the MySQL daemon.
CREATE USER MAPPING for postgres SERVER API OPTIONS ( username 'admin', password 'test');
-
Create a foreign table in your local database:
postgres=# CREATE FOREIGN TABLE contacts ( contacts_id text, contacts_Id text, contacts_DisplayName numeric) SERVER API OPTIONS ( table_name 'contacts');
postgres=# SELECT * FROM contacts;