Umed Khudoiberdiev
Umed Khudoiberdiev
Yes, if we would have this feature, it definitely needs to be as `{conflictPaths: {title: true}}` because we need to support columns inside embeds, e.g. `{ {conflictPaths: { nested: {...
I can accept it since it looks like doesn't break anything. Keep in mind embeds in entities are not supported by your changes. Later on we'll need to add this...
we actually must put `dataSource` into the interface and deprecate `connection`.
Imagine I added a new column to exist entity with a specific order. Then run synchronization. Will it work?
No, it won't work. Try it.
I think this is duplicate of #2199 ?
@teyou don't you think that adding similar check for postgres is going to solve this issue?
@anodynos are you sure its not supported by postgres, because looks like it does. And probably @andreasrueedlinger 's PR implement it, I just don't understand why we need a configuration...
Looks great, thank you for your hard work. This is huge feature to support... and to maintain. Usually people contribute and then disappear in a while (human factor I don't...
Feel free to contribute. You have to create PR against `0.3.0` branch since I guess it will be a breaking change.