My Hours → PlanetScale
AI-first ETL from My Hours into PlanetScale. Governed entities, incremental sync, typed landing tables.
How Datrise loads My Hours into PlanetScale
Datrise syncs My Hours's records, events, and configuration objects into PlanetScale as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME.
Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.
Ideal for horizontally scalable MySQL apps on Vitess.
Endpoints
My Hours: SaaS or API data source for analytics and warehouse sync.
PlanetScale: Serverless MySQL platform with safe schema workflows.
How My Hours entities map to PlanetScale
| My Hours entity | PlanetScale object | Notes |
|---|---|---|
| records | my_hours_records | id PK · custom fields → JSON columns |
| events | my_hours_events | DATETIME events |
| configuration objects | my_hours_configuration_objects | id PK · linked to my_hours_records |
FAQ
How does Datrise handle My Hours's custom fields in PlanetScale?
Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native PlanetScale types.
How does the My Hours to PlanetScale sync stay up to date?
It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.
Related pipelines
More destinations for My Hours
More sources for PlanetScale
Early access
Connect My Hours to PlanetScale 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.