Hey all, I have a quick question if you could help...
# singer-tap-development
d
Hey all, I have a quick question if you could help. I've been looking for a way to handle hard deletes in my data source and the two solutions I've seen are using
ACTIVATE_VERSION
as my singer table replication method, or using the Target Postgres variant transferwise to take advantage of the
_sdc_
metadata columns, then use dbt snapshots and so on. My question is, has anyone found/know of a work around to completely refresh a tap's stream table every sync? I could then just snapshot this table and capture deletes that way. Also are there any other methods for capturing hard deletes that I've missed? Wanted to see if this was a think before I commit to the whole
ACTIVATE_VERSION
refactor that I think I'm going to need to do. Thanks