Required Functionality
I want to use synth, however, one unsupported field type (see #305) currently blocks the complete import process.
Proposed Solution
Introduce a flag which skips over unsupported types and prints a warning, but keeps on processing supported types. When an unsupported type is encountered on a column with not null constraint, it should abort as generate data can not be imported into the DB in this case.
Use case
This allows to use and experiment with synth even if some converters are not available. Users with complex DB setups are not blocked on all converters being available which should help with adoption rate.
Required Functionality I want to use
synth
, however, one unsupported field type (see #305) currently blocks the complete import process.Proposed Solution Introduce a flag which skips over unsupported types and prints a warning, but keeps on processing supported types. When an unsupported type is encountered on a column with
not null
constraint, it should abort as generate data can not be imported into the DB in this case.Use case This allows to use and experiment with
synth
even if some converters are not available. Users with complex DB setups are not blocked on all converters being available which should help with adoption rate.