Club Speed to DuckDB Integration
AI-first ETL from Club Speed into DuckDB. Governed entities, incremental sync, typed landing tables.
How Datrise loads Club Speed into DuckDB
Datrise syncs Club Speed's customers, races, bookings, products, transactions, and memberships into DuckDB as a typed table per source entity in a DuckDB file. Flexible or custom fields land in JSON or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP WITH TIME ZONE.
Sync is incremental: Datrise uses rewrites changed entities into the local database (or Parquet) on each run, so re-runs update only what changed. Hive-partitioned Parquet by load date when exporting. DuckDB is single-writer and embedded, so Datrise produces a consistent file snapshot rather than concurrent streaming writes.
Ideal for local and notebook analytics without standing up a server.
Endpoints
Club Speed: Venue management for karting and entertainment centers.
DuckDB: In-process analytics database for fast local OLAP.
How Club Speed entities map to DuckDB
| Club Speed entity | DuckDB object | Notes |
|---|---|---|
| customers | clubspeed_customers | id PK · custom fields → JSON or STRUCT columns |
| races | clubspeed_races | id PK · linked to clubspeed_customers |
| bookings | clubspeed_bookings | id PK · linked to clubspeed_customers |
| products | clubspeed_products | id PK · linked to clubspeed_customers |
FAQ
How does Datrise handle Club Speed's custom fields in DuckDB?
Flexible values are stored as JSON or STRUCT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native DuckDB types.
How does the Club Speed to DuckDB sync stay up to date?
It runs incrementally — Datrise uses rewrites changed entities into the local database (or Parquet) on each run.
Related pipelines
More destinations for Club Speed
Early access
Connect Club Speed to DuckDB the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.