You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 23, 2024. It is now read-only.
In my meltano tap-oracle use case I do not have columns like "updated_at" for every table. It is also not possible to always add those. I've stumbled upon the pseudo_column ORA_ROWSCN which (as far as i understand) gets used by the extractor if a run is aborted. Would it be possible to also use the ORA_ROWSCN column as a replication_key to enable key-based incremental replication for tables without specific timestamp columns?
The text was updated successfully, but these errors were encountered:
In my meltano tap-oracle use case I do not have columns like "updated_at" for every table. It is also not possible to always add those. I've stumbled upon the pseudo_column ORA_ROWSCN which (as far as i understand) gets used by the extractor if a run is aborted. Would it be possible to also use the ORA_ROWSCN column as a replication_key to enable key-based incremental replication for tables without specific timestamp columns?
The text was updated successfully, but these errors were encountered: