Open source data anonymization and synthetic data orchestration for developers. Create high fidelity synthetic data and sync it across your environments.
This is problematic for any schema or table that has this character in it.
We kind of do this everywhere and should pick a different identifier to join them.
Separately, once we join them, we probably shouldn't separate them again unless we are sufficiently sure that the key is not capable of being a part of a schema or table (is this even possible to handle?)
This is problematic for any schema or table that has this character in it.
We kind of do this everywhere and should pick a different identifier to join them.
Separately, once we join them, we probably shouldn't separate them again unless we are sufficiently sure that the key is not capable of being a part of a schema or table (is this even possible to handle?)
From SyncLinear.com | NEOS-1626