The CData JDBC Driver for Act-On models entities in the Act-On API as tables, views, and stored procedures. These are defined in schema files, which are simple, text-based configuration files.
Lists in Act-On are exposed as views with the convention List_ListName. For each list there is another view List_ListName_Score where you can see the score of the people in the list.
Same logic for Segments in Act-On, they are exposed as views as Segment_SegmentName. And have an equivalent view Segment_SegmentName_Score.
Any changes you make to your Act-On account, such as adding a new list, adding new columns, or changing the data type of a column, will immediately be reflected
when you connect using the driver.
Using Collaborative Query Processing
The driver offloads as much of the SELECT statement processing as possible to the Act-On APIs and then processes the rest of the query within the driver. The following sections document API limitations and requirements. See SupportEnhancedSQL for more information on how the driver circumvents API limitations with in-memory client-side processing.
Views are tables that cannot be modified. Typically, read-only data are shown as views.
Stored Procedures are function-like interfaces to the data source. They can be used to search, update, and modify information in the data source.