Database Reference
Known limitations
The source tables hold current state only. Plan your pipeline around these two gaps.
No row-level change history#
Each row stores only its latest state. You cannot tell how many times a row changed, or what values it held before — only what it looks like now, and when it last changed (updated_at).
Implication
If you need history (for example, when an order's status changed), you must capture it yourself by keeping snapshots or an append-only log in your destination each time you load.
No delete tracking#
When a row is deleted it simply disappears from query results. There is no tombstone and no record that it ever existed, so an updated_at filter will never surface a deletion.
Implication
Incremental loads cannot detect deletes. If your destination must mirror deletions, you need a periodic reconciliation, such as comparing the full set of
ids in the source against your copy.Summary#
- Latest state only — no history of intermediate changes.
- Deleted rows vanish silently.
- Both limits apply to the REST API and to direct database access.
© 2026 StyleHub · Developer Platform