The driver models SendGrid APIs as relational tables, views, and stored procedures. Most tables, views, and stored procedures are defined in schema files, which are simple, text-based configuration files.
However, the Recipients table is dynamic: The driver connects to SendGrid and gets the metadata for this table by calling the appropriate Web services. Any changes you make to the custom filters you define for Recipients are available when you connect; you can use these custom filters as columns in the WHERE clause. These custom filters are surfaced in the CustomFields table.
API limitations and requirements are documented in this section; you can use the SupportEnhancedSQL feature, set by default, to circumvent most of these limitations.
TablesThe driver models the SendGrid API as relational Tables that are easy to query and update.
In addition to the tables, the driver also offers stored procedures and views, enabling you to work with other aspects of the SendGrid API, like adding recipients to lists, reporting statistics, etc.
Stored Procedures are function-like interfaces to Sendgrid. They can be used to search, update, and modify information in SendGrid.
Views are tables that cannot be modified. Typically, read-only data are shown as views.