duckdb/replace.sql

{{- /* replace.sql — delete all rows then re-insert the full staging set (no versioning). */ -}}
{{- /* DELETE FROM rather than TRUNCATE: proven legacy behavior, and both statements run  */ -}}
{{- /* in ONE transaction (rdbms.ExecStatements), so a failed re-insert rolls the delete  */ -}}
{{- /* back.                                                                              */ -}}
DELETE FROM "{{ .HistorySchema }}"."{{ .HistoryTable }}";

INSERT INTO "{{ .HistorySchema }}"."{{ .HistoryTable }}" (
    {{ template "business_col_list" . }}, {{ template "amf_system_cols" . }}
)
SELECT {{ template "business_col_list" . }}, {{ template "amf_system_vals" . }}
FROM   "{{ .StagingSchema }}"."{{ .StagingTable }}" stg