The CData Python Connector for Google Calendar models Google Calendar APIs as relational tables, views, and stored procedures. API limitations and requirements are documented in this section; you can use the SupportEnhancedSQL feature, set by default, to circumvent most of these limitations.

Tables

The connector dynamically retrieves table definitions for the calendars accessible to your account. Tables describes the columns for a sample calendar as well as the Calendars table, which can be used to list, create, modify, and delete calendars.

Views

Views offer additional metadata information from Google Calendar to surface other aspects of a calendar.

Stored Procedures

Stored Procedures are function-like interfaces to the data source.

Key Features

Working with event-related entities

When working with events and their related entities through: EventsAttachments, AllCalendars, or dynamic event tables, only single events and recurring events (with their exceptions) are included by default, but not recurring event instances. To change this behavior, you can use EventsScope.

Note: Exceptions are recurring event instances that differ from their parent recurring event in any way.

Note: Single events are non-recurring events.

Working with Deleted Events

When working with events and their related entities through: EventsAttachments, AllCalendars, or dynamic event tables, deleted/cancelled events are not included by default. To change this behavior, you can enable ShowDeleted or use the pseudo-column in the corresponding table/view. In that case, events with the status 'cancelled' are included in the results. The value specified in the pseudo-column will take higher precedence then the value specified in ShowDeleted.