acuthbert

We've had some internal conversations about this today and wanted to float a second solution. Should the meta data for the mapping be inferred from the relation you're trying to...

This would also get around the need to pass over the second last optional argument with 'undefined' :joy:

I've posted a potential solution for this: https://github.com/typeorm/typeorm/pull/9354

From what I can see the issue is that unless you use an Entity class or a relation property, typeorm cannot know what the mappings are from the properties on...

@prateekkathal I've created an MR to fix this - although the user has to pass the entity for the mapping as it might not always be able to get this...

We are also getting the same issue. We did nothing except update packages recently and this error has started to appear since moving to this version.

Actually scratch that - in fact this package hasn't updated but the error has only started to occur recently so perhaps an issue in other depedancies is causing this?

@cjsauer I just came across your comment today. Can you have a look at the [Files Changed ](https://github.com/typeorm/typeorm/pull/9354/files) on this MR as I can't see how the added code could...

> I figured out my problem, the user I was using was incorrect. Azure requires users in the form `user@databasename` and I was only using `user`. > > This can...

This would be a really useful feature for complex projects where base types and entities are used in multiple controllers in very different security contexts - and where Exclude() on...