# singer-tap-development


09/07/2021, 10:38 AM
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
as my singer table replication method, or using the Target Postgres variant transferwise to take advantage of the
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
refactor that I think I'm going to need to do. Thanks