singer-io/tap-postgres

default Boolean values set as nulls when false

Closed this issue · 1 comments

While copying data from a Postgres table defined with a default Boolean value (default is false), the resulting data in the target database contains null values rather than false. The column is not-null in the source database so is always either true or false.

It looks like I was premature in blaming tap-postgres for this issue. The problem apparently really lay with target-postgres. Switching to another implementation of target-postgres resolved the issue.