Include all _sdc_ meta columns on all synced tables

[paulhansen-dx]

Stitch only adds the _sdc_deleted_at meta column when a deleted record is first discovered.
Is there any reason all meta columns cannot be added at the time of the first sync when the destination tables are created by Stitch, regardless of whether or not hard deletes ever occur in the source db? This seems consistent regardless of which database integration is being used.

Summary: Add _sdc_deleted_at column to all destination tables regardless of the existence of a delete event.

[bibli-alex]

We've just run into this issue too - if the table is using log-based replication, it should always include the column. The fact that they're all NULL is immaterial - our models in our transformations rely on that column existing so that when they become not-null in the future, the code will be there to handle it.

[lewisarmistead]

This feature would reduce our overhead of detecting and measuring deletes by allowing us to run tests using that _sdc_deleted_at field for new log-based replication sources right after their first sync rather than either waiting for the first deletion or incorporating conditional logic to accommodate the missing field.

[lukegenung]

This seems like a major oversight, especially since this approach to filtering rows WHERE _sdc_deleted_at IS NULL is how the Stitch docs recommend handling hard deletes. Instead, I just did WHERE COALESCE(created_at, updated_at) IS NOT NULL . This makes Stitch's metadata columns and docs kind of useless.