Marcel Bradea

PS: We would not have to be going through this pain if the team didn't abandon EF6 before EF Core is ready. Are cross-platform migrations EVER going to be supported...

@ErikEJ not saying you can't. But we have a not *THAT* complex system, and when you can't even compare a list of stings in a query, let alone the bigger...

This would be extremely useful. Currently anything other than simple "complex" structures aren't supported by EF Owned Types (either multi-column-mapped or JSON-column-mapped), limiting their use and having to fall back...

Please keep us posted on this @vivet I know it's likely not a trivial migration, but would be great to get a branch going with a head start on it...

Not sure in which EF/ASP.NET version this started happening in but our EF migrations have started facing this problem as well. We are still using the traditional web host builder...

+1

One workaround we've used as a way of getting around this limitation is to create an 'id' property which simply concatenates the different fields that you want to use in...

@realpunk yup I think that's the recommended workaround. It's probably why the team hasn't been prioritizing this very much - along with the fact that Realm doesn't really expose foreign...

Thanks so much for chasing this down @cosmer-work! We were blocked on migrating recently and had to reshuffle around some work thinking we'd have to put in some extra synchronization...

Guys this should be prioritized. The whole point of an ORM is to Map to Objects... and EF has traditionally stood out particularly due to its ability to map to...