You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 30, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: docs/docs/guides/new-column-addition-strategies.md
+14-6Lines changed: 14 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,6 +55,14 @@ The algorithm works as follows:
55
55
3. Based on the data type, generate a proper value that will fit within that column.
56
56
4. If an unsupported data type is detected, halt the run.
57
57
58
+
## Passthrough
59
+
60
+
Passthrough mode is a strategy that allows Neosync to handle new columns found in source tables by setting them to passthrough. This means that any new columns detected in the source database will be included in the table sync and their values will be directly copied from the source to the destination without any transformation.
61
+
62
+
This strategy is useful when you want to reduce the need for manual updates to job mappings when new columns are added to the source database.
63
+
64
+
**Note:** It is recommended to use the init schema destination option with the passthrough strategy to ensure that the destination schema is always updated to match the source schema.
65
+
58
66
### Postgres
59
67
60
68
Postgres has many data types and not all of them are currently supported in the auto map mode. Support will continue to increase over time.
@@ -78,12 +86,12 @@ Postgres has many data types and not all of them are currently supported in the
0 commit comments